2 ms·
HTTP 2.0 will still be defined for unencrypted operation, for deployment on Intranets. This default is for the open web. Since a number of people don't seem t
by parasubvert 13y ago
HTTP 2.0 will still be defined for unencrypted operation, for deployment on Intranets. This default is for the open web.
Since a number of people don't seem to be reading TFA, I'll help:
"To be clear - we will still define how to use HTTP/2.0 with http:// http:// URIs, because in some use cases, an implementer may make an informed choice to use the protocol without encryption. However, for the common case -- browsing the open Web -- you'll need to use https:// https:// URIs and if you want to use the newest version of HTTP."
- zurn 13y agoThat's not what the proposals A and B say - only C says http:// http:// would be cleartext. Also the followup message(s) say the poster misrepresents the C option presented at the meeting. See http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0629.html http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/...