We have made changes with regard to parsing of response headers for XHR and fetch for the Bug 1697421. The changes have fixed the General header combining problem mentioned in the bug Description. As a result we could see that the wpt cases added for this bug (https://github.com/web-platform-tests/wpt/pull/13471) are passing: https://wpt.fyi/results/fetch/api/basic/header-value-combining.any.html?label=master&label=experimental&aligned&view=subtest&q=header-value-combining https://wpt.fyi/results/xhr/getallresponseheaders.htm?label=master&label=experimental&aligned&view=subtest&q=getallresponseheaders.htm https://wpt.fyi/results/xhr/getresponseheader.any.worker.html?label=master&label=experimental&aligned&view=subtest&q=getresponseheader.any However, we still have the following issues within the scope of this Bug: Issue 1. content-length parsing https://wpt.fyi/results/fetch/content-length/parsing.window.html?label=master&label=experimental&aligned&view=subtest&q=parsing.window Issue 2. x-content-type options parsing https://wpt.fyi/results/fetch/nosniff/parsing-nosniff.window.html?label=master&label=experimental&aligned&view=subtest&q=parsing-nosniff.window Issue 3. Content-type parsing in general does not completely adhere to the fetch spec. Issue 3 is tracked by Bug 1510180. I propose to fix Issue 1 and Issue 2 with this Bug.
Bug 1499356 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We have made changes with regard to parsing of response headers for XHR and fetch for the Bug 1697421. The changes have fixed the General header combining problem mentioned in the bug Description. As a result we could see that the wpt cases added for this bug (https://github.com/web-platform-tests/wpt/pull/13471) are passing: https://wpt.fyi/results/fetch/api/basic/header-value-combining.any.html?label=master&label=experimental&aligned&view=subtest&q=header-value-combining https://wpt.fyi/results/xhr/getallresponseheaders.htm?label=master&label=experimental&aligned&view=subtest&q=getallresponseheaders.htm https://wpt.fyi/results/xhr/getresponseheader.any.worker.html?label=master&label=experimental&aligned&view=subtest&q=getresponseheader.any However, we still have the following issues within the scope of this Bug: Issue 1. content-length parsing https://wpt.fyi/results/fetch/content-length/parsing.window.html?label=master&label=experimental&aligned&view=subtest&q=parsing.window Issue 2. x-content-type options parsing https://wpt.fyi/results/fetch/nosniff/parsing-nosniff.window.html?label=master&label=experimental&aligned&view=subtest&q=parsing-nosniff.window Issue 3. Content-type parsing in general does not completely adhere to the fetch spec. Issue 3 is tracked by Bug 1510180. I propose to fix only Issue 1 and Issue 2 with this Bug.