New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes for HTTP header compliance. #32024
Conversation
4389ae6
to
2da8fd6
Compare
It looks like this change is failing unit tests |
- Fix 400 errors from nginx in response to Servo requests by implementing conformant albeit non-normative removal of whitespace from `Accept` and `Accept-Language` HTTP headers. (To match behaviour of Firefox, Safari, and Chrome) https://datatracker.ietf.org/doc/html/rfc7231#section-5.3.2 - Provide `Host` header as REQUIRED by HTTP protocol https://www.rfc-editor.org/rfc/rfc9110#field.host - Update tests.
2da8fd6
to
84811aa
Compare
🔨 Triggering try run (#8638578462) for Linux WPT |
Test results for linux-wpt-layout-2020 from try job (#8638578462): Flaky unexpected result (22)
Stable unexpected results that are known to be intermittent (9)
|
✨ Try run (#8638578462) succeeded. |
These changes look reasonable to me. I swear hyper used to always provide the host header, but maybe that changed. |
Thanks Josh. |
servo#32024 broke a different set of nginx sites, and a more sophisticated fix for the case of a missing HTTP 1.1 `Host` header is required.
Unfortunately, this change breaks a different set of nginx sites, so |
Accept
andAccept-Language
HTTP headers. (To match behaviour of Firefox, Safari, and Chrome) https://datatracker.ietf.org/doc/html/rfc7231#section-5.3.2Host
header as REQUIRED by HTTP protocol https://www.rfc-editor.org/rfc/rfc9110#field.host./mach build -d
does not report any errors./mach test-tidy
does not report any errors