Re: [whatwg/fetch] Handling of invalid Location header characters doesn't match browsers (#883) from David Benjamin on 2019-03-23 (public-webapps-github@w3.org from March 2019)

From: David Benjamin <notifications@github.com>
Date: Sat, 23 Mar 2019 06:25:06 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/883/475869545@github.com>

Oh, interesting. `HttpResponseHeaders::IsRedirect` still believes it's possible. I guess we missed updating that comment.

Although I see that this check is implemented in the HTTP/1.1 parser (which makes sense since HTTP/1.1 is the one with the absurdly fragile text encoding), so it may differ in HTTP/2 and QUIC, just to make things more fun...

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

Received on Saturday, 23 March 2019 13:25:27 UTC