Re: [whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609) from Thomas Wisniewski on 2018-02-20 (public-webapps-github@w3.org from February 2018)

From: Thomas Wisniewski <notifications@github.com>
Date: Tue, 20 Feb 2018 07:37:01 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/609/367016798@github.com>

I just closed XHR issue 192 (https://github.com/whatwg/xhr/issues/192) of this, but was wondering if the inconsistency I found there is related to this. Browsers are currently passing the "301 POST with string and explicit Content-Type safelisted" XHR WPT in /xhr/send-redirect-to-cors.htm, but I don't believe they should if we're meant to strip these content- headers (since it's a 301 redirect that expects the body to be nulled, so it seems it should not be expecting the content-type to remain).

-- 
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/609#issuecomment-367016798

Received on Tuesday, 20 February 2018 15:37:58 UTC