4 ms·
This is only for HTTP/2. If could have been for HTTP/1.1 also, if there had existed a registered ALPN name for “HTTP/1.1 with TLS”. As it is now, HTTP/2 has b
by teddyh 12y ago
This is only for HTTP/2. If could have been for HTTP/1.1 also, if there had existed a registered ALPN name for “HTTP/1.1 with TLS”. As it is now, HTTP/2 has both variants, but HTTP/1.1 stands alone¹.
① https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids https://www.iana.org/assignments/tls-extensiontype-values/tl...
- patrickmcmanus 12y agofwiw the h1 barrier was the lack of a scheme indication in an h1 transaction - not really the alpn ids (which can always be registered if need be). But without a scheme the server just needs to infer http vs https from the port/address and that wouldn't work with alt-svc
- teddyh 12y agoSince this is a backport of a new feature from a new protocol to its older predecesor protocol, it is not necessary to be so wary of slightly uglier features. Simply having “Alt-Svc: http/1.1:443” imply HTTPS would do fine to solve this specific problem, and I doubt anyone would really have a problem with it.