Re: [whatwg/fetch] strip request-body-header for redireting from POST to GET (#977)

I don't think `Content-Encoding: chunked` means anything, so it shouldn't be any different from `Content-Encoding: garbage`. While `Transfer-Encoding` nominally can also do compression, I don't think any browser supports it.

The two are effectively orthogonal. `Content-Encoding` is whether there is compression applied to the body and should be supplied by whoever supplied the body. `Transfer-Encoding` is largely a symptom of HTTP/1.1's poor layering. It should be supplied by the low-level HTTP/1.1 (and not HTTP/2) encoding logic, well below Fetch and the web platform. Alas, HTTP headers are a leaky abstraction, so we're stuck needling to forbid `Transfer-Encoding` at the Fetch level, but we should layer things so we otherwise don't need to think about it.

-- 
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/pull/977#issuecomment-561738739