Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) from Richard Gibson on 2024-08-19 (public-webapps-github@w3.org from August 2024)

From: Richard Gibson <notifications@github.com>
Date: Mon, 19 Aug 2024 09:43:30 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/883/2296996987@github.com>

Right, it's currently just under the undefined behavior umbrella of [RFC 9110 Error Handling](https://www.rfc-editor.org/rfc/rfc9110.html#section-2.4):
> Unless noted otherwise, a recipient **MAY** attempt to recover a usable protocol element from an invalid construct… For example, a Web browser might wish to transparently recover from a response where the <a href="https://www.rfc-editor.org/rfc/rfc9110.html#field.location">Location</a> header field doesn't parse according to the ABNF

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

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

Received on Monday, 19 August 2024 16:43:34 UTC