- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 31 Jan 2017 05:02:16 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 31 January 2017 13:02:54 UTC
See https://github.com/w3c/wptserve/issues/112 for what is blocking tests. See https://github.com/w3c/web-platform-tests/commit/e94ccfed3a3ec91cb357fd6684caa2d065b34ae8 for some test sketches. The change shouldn't affect any JavaScript API behavior. They will still expose header names as lowercase even though the case given by the developer is used on the network. (Though see https://github.com/whatwg/xhr/issues/108 and https://github.com/whatwg/xhr/issues/109 for discussions on that front with regards to XMLHttpRequest, which ideally is somewhat aligned.) If we want a discussion on whether to allow case normalization for known headers to happen (Firefox and Safari do this) we should do that through a separate issue. For now I noted it in the source that this is a thing. I would appreciate review from @younnf and @jdm. You can view the specification with this PR applied at https://fetch.spec.whatwg.org/branch-snapshots/annevk/header-names/. Hopefully that simplifies reviewing. (Click in the title of the red blob to hide 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/476#issuecomment-276357244
Received on Tuesday, 31 January 2017 13:02:54 UTC