With Chrome, about 0.003% of main frame responses are detected as HTTP/0.9, and 0.005% of subresources are HTTP/0.9. Since HTTP/0.9 includes no explicit identifying headers, some of these could be broken servers responding with nonsense data. We actually did try to go it alone in remove HTTP/0.9 support, but soon backed off after trying it in our pre-release channels, because of the aforementioned incident with the configuration page of a line of home routers. On Wed, Oct 19, 2016 at 4:57 AM, Frederik Braun <fbraun@mozilla.com> wrote: > On 17.10.2016 23:43, Daniel Stenberg wrote: > > On Mon, 17 Oct 2016, Poul-Henning Kamp wrote: > > > >> Do you really still see HTTP/0.9 reponses in the wild ? > > > > Yes. Of course subject to debate around what "in the wild" means... > > > > There was a recent security bug with regards to HTTP/0.9 compat [1] that > suggested a coordinated fix among multiple browsers. Browser vendors > decided that they'd start off killing HTTP/0.9 compat on non-standard > ports only, because overall usage was still too high. > Firefox has HTTP 0.9 usage data[2] and so do other browsers. Please > chime in. > > Hope that helps, > Frederik > > > > [1] See entry in Bugzilla with links to Webkit and Chrome bug: > https://bugzilla.mozilla.org/show_bug.cgi?id=1262128 > [2] I'm new to our telemetry dashboard, so maybe there could be a more > useful graph than this one > https://telemetry.mozilla.org/new-pipeline/dist.html#! > cumulative=0&end_date=2016-09-22&keys=__none__!__none__!__ > none__&max_channel_version=release%252F49&measure=HTTP_ > 09_INFO&min_channel_version=null&product=Firefox!Fennec& > sanitize=1&sort_keys=submissions&start_date=2016-09-16&table=0&trim=1&use_ > submission_date=0 > > >
Received on Wednesday, 19 October 2016 14:31:37 UTC