Firefox, Chrome, and IE only support HTTP/2 over TLS, even though the
spec does not require it. What if browser vendors similarly agreed to
never send the User-Agent header over HTTP/2?
If legacy content relies on User-Agent checks, it could:
* Stick with HTTP/1.1.
* Use HTTP/2 connection upgrade from HTTP/1.1, grabbing the User-Agent
header on the initial HTTP/1.1 connection.
* Check navigator.userAgent on the client.
If we can't kill the User-Agent header at this juncture, then when? :)
btw, here is the "spartan" User-Agent string for Microsoft's new Spartan
browser:
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0
(Conspicuously missing: any mention of MSIE or Trident.)
chris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
