[whatwg/fetch] Should Content-Type header be stripped when redirecting from POST to GET? (#609)

The reporter of Chrome issue https://bugs.chromium.org/p/chromium/issues/detail?id=765898 ("XHR preserves Content-Type on cross-origin 303 redirect") argues that when a 303 redirect causes a request to be redirected from POST to GET and the request body stripped, the Content-Type header should also be removed.

Chrome's current behaviour differs depending on the type of fetch that is being performed.

Before settling on a single behaviour in Chrome it would be nice to be definitive about what the standard behaviour is.

My understanding from reading the above Chrome issue is that the standard currently implies that the header is not removed, but removing it has better compatibility with servers.

-- 
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