- From: youennf <notifications@github.com>
- Date: Fri, 15 Jan 2016 05:28:52 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/189/171962007@github.com>
Let's take that header set as example: Name: value1, value2 Name: value3 If the header set is part of a response, how will be presented this data to a web application by the fetch API? Is it the case that some web engines will present to web applications a response header structure with two entries while some other web engines will present to web applications a response header structure with one entry? Or is one correct and not the other? If both are ok, one web engine may return "value1, value2" when calling get("Name") while the other will return "value1, value2, value3". getAll is similar in spirit here ([[value, value2], value3] vs. [[value1, value2, value3]]). If the header set is part of a request, the corresponding request at the protocol level can use one or two headers, it will be semantically equivalent. What is the benefit of enabling a web application query whether there is one combined header or two headers with the same name? --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/189#issuecomment-171962007
Received on Friday, 15 January 2016 13:29:19 UTC