- From: Anne van Kesteren <notifications@github.com>
- Date: Thu, 09 Feb 2017 00:26:29 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 9 February 2017 08:27:03 UTC
annevk commented on this pull request. > -<a>header</a> whose <a for=header>name</a> -is <var>name</var>, <a lt="byte-lowercase">byte-lowercased</a>, and -<a for=header>value</a> is <var>value</var>, to -<var>list</var>. +<a for=header>name</a>/<a for=header>value</a> (<var>name</var>/<var>value</var>) pair to a +<a for=/>header list</a> (<var>list</var>), run these steps: + +<ol> + <li> + <p>If <var>list</var> <a for="header list">contains</a> <var>name</var>, then set <var>name</var> + to the first such <a>header</a>'s <a for=header>name</a>. + + <p class="note no-backref">This reuses the casing of the <a for=header>name</a> of the + <a>header</a> already in the <a for=/>header list</a>, if any. If there are multiple matched + <a>headers</a> their <a for=header>names</a> will all be identical. + <!-- XXX Firefox and Safari adjust known header names too. --> Note that all browsers currently make it observable through `getAllResponseHeaders()` so we might still get stuck there one way or another. If we are to allow the user agent to pick casing for well-known headers I think we should probably standardize that and get everyone on board. Seems like it would be best done as a new issue. -- 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
Received on Thursday, 9 February 2017 08:27:03 UTC