Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883)

The `Location` header field value is specified by [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#field.location) to be an [RFC 3986 URI-reference](https://www.rfc-editor.org/rfc/rfc3986.html#section-4.1) (_which does not allow characters outside the ASCII range or quirks such as [tab inside a host domain name label](https://github.com/whatwg/url/issues/829)_), and this issue—among others—documents an intentional divergence from those other specifications. Is there a plan to update the IANA registration for `Location` and other header fields whose value syntax includes URI-reference (e.g., [`Link`](https://www.rfc-editor.org/rfc/rfc8288.html#section-3)), resolving the inter-specification incompatibilities? This seems similar to the problems addressed by [ECMA-262 Annex B](https://tc39.es/ecma262/multipage/additional-ecmascript-features-for-web-browsers.html#sec-additional-ecmascript-features-for-web-browsers), which strives to precisely document the ways in which web browser behavior deviates from a simpler and stricter core specification.

cc @mnot

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/883#issuecomment-2294982814
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/883/2294982814@github.com>