Menu
I saw that URLSession supports HTTP 1.1 and HTTP 2 (URLSession supports the HTTP/1.1 and HTTP/2 protocols).
How can I enforce URLSession to use HTTP1.1?
794
When to switch? Switching to HTTP/2 is a decision to made after analysing the browser version data of your user base. The HTTP/1.1 to HTTP/2 protocol conversion happens automatically and its backward compatible. So there is nothing pretty much to be done to switch it other than ensuring your server supports it.
Yes, mostly. For HTTP/2 over TLS ( h2 ), if you do not implement the http1. 1 ALPN identifier, then you will not need to support any HTTP/1.1 features. For HTTP/2 over TCP ( h2c ), you need to implement the initial upgrade request.
The answer here is no: the HTTP/2 support is part of iOS 9, and thus won't be available on earlier OS releases.
HTTP2 is much faster and more reliable than HTTP1. HTTP1 loads a single request for every TCP connection, while HTTP2 avoids network delay by using multiplexing. HTTP is a network delay sensitive protocol in the sense that if there is less network delay, then the page loads faster.
Not exactly, there is ALPN negotiation to decide if HTTP/2. If client does not send ALPN, then server should not use HTTP/2.
37
This is not something determined by the URLSession. It is determined by the server it connects to.
Read more on that here... https://forums.developer.apple.com/thread/94907
186
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
