Re: [whatwg/fetch] Optional disable setting headers keys in lowercase (#304) from Anne van Kesteren on 2017-01-30 (public-webapps-github@w3.org from January 2017)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 30 Jan 2017 05:36:54 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/304/276064086@github.com>

@youennf so it seems Firefox and Safari have atom-lists of builtin headers, but as far as I can tell Chrome and Edge do not. E.g., they do not change `CONTENT-LENGTH` in a response to `Content-Length` (can be observed through XMLHttpRequest's `getAllResponseHeaders()`).

Another problem here is that wptserve from web-platform-tests does not allow inspection of the request headers to the detail of the casing used. @jgraham is that correct or did I miss something?

https://github.com/whatwg/xhr/issues/108 also has some discussion of related issues.

I guess I can work on a patch that preserves casing and then open a new issue with regards to builtin header names. Still, it would be good to actually be able to test things in some manner.

-- 
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/304#issuecomment-276064086

Received on Monday, 30 January 2017 13:37:26 UTC