- From: Anne van Kesteren <notifications@github.com>
- Date: Tue, 26 Nov 2019 09:52:47 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 November 2019 17:52:50 UTC
As far as I know request header name casing is exposed to servers when using h1 (though you cannot have case-insensitive duplicates with different casing). Order of request headers isn't really defined, though I maybe that means insertion order? Response headers are always normalized to lowercase. They are also ordered lexicographically though XMLHttpRequest orders slightly differently (uppercases first). Some of these characteristics are worth mentioning in a note I think as they are relevant for implementations and it would be good if they didn't have to derive this from the various places that expose headers. (If h1 disappears this will be less of an issue since presumably future iterations of the protocol won't reintroduce design issues like this.) -- 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/972
Received on Tuesday, 26 November 2019 17:52:50 UTC