IOS9 all HTTP requests to https: The IOS9 system sends a network request that uses TLS 1.2 SSL uniformly. With the TLS 1.2 protocol, the purpose is to enforce enhanced data access security, and related network requests under the System Foundation framework will no longer default to unsecured network protocols such as Http, and TLS 1.2 is used by default. The server therefore needs to be updated to parse the relevant data. If not updated, you can reverse the unsecured network request by declaring it in Info.plist.
Before the discussion, as usual, first of all, The iOS program apes are most concerned about the problem:
Have a hair relationship with me? Do you need me to work overtime?
First, let's look at the industry's comments on Apple's approach:
This is a social app to discuss, it seems that the industry is still spit sound and affirmation of the sound of the same.
The conclusion is:
I have a relationship with you, work overtime, Junior!
The book "Serious Face", we formally discuss the following what,why,how:
-
What is SSL/TLS? What is the relationship with HTTP and HTTPS?)
-
Why (previous HTTP is not also available?) Why use SSL/TLS, idle panic?! Is Apple again anti-human? )
-
How (How to fit?) ---weak and weak to ask: how long to work overtime? )
What is SSL/TLS? What is the relationship with HTTP and HTTPS?)
As usual, let's start with the conclusion that:
| 1 |
HTTP+SSL/TLS+TCP = HTTPS |
TLS is a new nickname for SSL. As an example:
"TLS1.0" to "SSL3.1", still "A.D. 2015" in the "Republic of 104", or "1 kilograms" to "one kilogram", or "half catty" to "82": The name is different, but the meaning is the same.
The iteration version after the SSL 3.0 version is renamed to TLS 1.0,
Other words:
So they're a thing, and we often simply see the term "SSL/TLS".
Commonly used are the following:
-
SSL 2.0
-
SSL 3.0
-
TLS 1.0 (SSL 3.1)
-
TLS 1.1 (SSL 3.1)
-
TLS 1.2 (SSL 3.1)
So why is the title "using HTTPS" without mentioning SSL and TLS? To understand this, take a look at the next formula:
| 1 |
HTTP+SSL/TLS+TCP = HTTPS |
For example: If the original HTTP is a plastic pipe, easy to be punctured, then the new design of HTTPS today is like in the original plastic pipe, and then a layer of metal pipe. As a result, the original plastic pipe is still running, and secondly, after being reinforced with metal, it is not easy to be punctured.
Currently, the most widely used is TLS 1.0, followed by SSL 3.0. However, the majority of browsers have implemented TLS 1.2 support.
Apple lets your HTTP use the SSL/TLS protocol, which lets you go from http to https
Why (previous HTTP is not also available?) Why use SSL/TLS, idle panic?! Is Apple again anti-human? )
HTTP communications that do not use SSL/TLS are non-encrypted communications!
All information is transmitted in plaintext, bringing three major risks:
-
Eavesdropping risk (eavesdropping): Third parties can learn the content of the communication.
-
Tamper risk (tampering): Third parties may modify the communication content.
-
Impersonation risk (pretending): A third party can participate in the communication by impersonating another person.
The SSL/TLS protocol is designed to address these three risks and is expected to achieve:
-
All information is encrypted and third parties cannot eavesdrop.
-
With the verification mechanism, once tampered with, the communication parties will immediately find.
-
Equipped with identity card to prevent identity from being impersonated.
How (How to fit?) ---weak and weak to ask: how long to work overtime? )
As the beginning of the article says:
The TLS 1.2 protocol enforces enhanced network requests under the framework of the data access security system Foundation and will no longer default to unsecured network protocols such as Http, with TLS 1.2 being used by default. The server therefore needs to be updated to parse the relevant data. If not updated, you can reverse the unsecured network request by declaring it in Info.plist.
Scenario One: Immediately let the company's server upgrade use TLS 1.2
Scenario Two: Although Apple does not recommend, but can be declared in the Info.plist, back to the insecure network request will still allow the app to access the specified HTTP, or even arbitrary HTTP,
See GIF diagram for a sample demo see Demo1
As the official Apple document says:
The XML source in the Info.plist configuration is as follows:
| 1234 |
nsapptransportsecurity nsexceptiondomains yourserver.com nsincludessubdomains nstemporaryexceptionallowsinsecurehttploads nstemporaryexceptionminimumtlsversion tlsv1.1 |
If your application (a Third-party Web browser, for instance) needs to connect to arbitrary hosts, you can configure it Li Ke this:
| 12 |
NSAppTransportSecurity NSAllowsArbitraryLoads |
HTTP and HTTPS