Open Bug 1540947 Opened 5 years ago Updated 2 years ago

Consider disabling HTTP/0.9 on Nightly

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

People

(Reporter: annevk, Unassigned)

Details

(Whiteboard: [necko-triaged])

According to mt there is no usage on Nightly and Beta. Seems like it's time to start deprecating it and perhaps let folks on Nightly run into issues when they encounter it anyway.

Last attempt by Google: https://groups.google.com/a/chromium.org/d/msg/blink-dev/OdKnpLlvVUo/1EpFGVUjAwAJ

Do we recognize a 'true' H.9 response from a broken (out of framing) server responses? - if that is even possible...

(In reply to Honza Bambas (:mayhemer) from comment #2)

Do we recognize a 'true' H.9 response from a broken (out of framing) server responses? - if that is even possible...

it is not possible. We do recognize 0.9 on a non-standards port, which are provably 'true' 0.9

https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2019-03-17&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F67&measure=HTTP_09_INFO&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_by_value=0&sort_keys=submissions&start_date=2019-01-28&table=0&trim=1&use_submission_date=0

Priority: -- → P3
Whiteboard: [necko-triaged]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.