262635 2023-10-04 11:21:49 -0700 FetchResponse.formData() should parse headers names as case insensitive 2023-10-10 09:13:17 -0700 1 1 1 Unclassified WebKit WebCore Misc. Safari 17 All All RESOLVED FIXED https://github.com/web-platform-tests/wpt/pull/42455 https://jsfiddle.net/x0o1mqj8/ InRadar P2 Critical --- 1 jimmy mike achristensen annevk cdumez mike webkit-bug-importer youennf oldest_to_newest 1982504 0 jimmy 2023-10-04 11:21:49 -0700 ## reproducible code: async function init() { var fd = new FormData() fd.set('x', 'y') var blob = await new Response(fd).blob() var body = await blob.text() blob = new Blob([body.toLowerCase()], { // convert boundary to lowercase also. type: blob.type.toLowerCase() }) fd = await new Response(blob).formData() console.log([...fd]) } init() ## Test page: https://jsfiddle.net/x0o1mqj8/ Works in Firefox, and all chromium browsers fails in safari 1982827 1 mike 2023-10-05 05:36:06 -0700 Pull request: https://github.com/WebKit/WebKit/pull/18689 1982828 2 mike 2023-10-05 05:42:21 -0700 If we do actually want to have interop on this, I can add WPT tests to the PR — and also I guess, update the algorithm at https://fetch.spec.whatwg.org/#dom-body-formdata to explicitly that the Content-Disposition and Content-Type headers names must be parsed case-insensitively. (Though, as noted in the comment which follows that algorithm in the spec: The algorithm is just “a rough approximation of what is needed for multipart/form-data” — that is, it’s already recognized to be underspecified…) 1983996 3 mike 2023-10-10 08:43:20 -0700 Submitted web-platform-tests pull request: https://github.com/web-platform-tests/wpt/pull/42455 1984009 4 ews-feeder 2023-10-10 09:12:31 -0700 Committed 269144@main (d0c370d532ad): <https://commits.webkit.org/269144@main> Reviewed commits have been landed. Closing PR #18689 and removing active labels. 1984010 5 webkit-bug-importer 2023-10-10 09:13:17 -0700 <rdar://problem/116742000>