RESOLVED CONFIGURATION CHANGED 46147
XMLHttpRequest: charset replacement algorithm doesn't fully match the spec 
https://bugs.webkit.org/show_bug.cgi?id=46147
Summary XMLHttpRequest: charset replacement algorithm doesn't fully match the spec
Jian Li
Reported 2010-09-20 17:45:51 PDT
XMLHttpRequest: send() does not set Content-Type header correctly if the Content-Type header is set using setRequestHeader() Per XHR spec: If a Content-Type header is set using setRequestHeader() whose value is a valid MIME type and has a charset parameter whose value is not a case-insensitive match for encoding, and encoding is not null, set all the charset parameters of the Content-Type header to encoding. Test: http://tc.labs.opera.com/apis/XMLHttpRequest/send-content-type-charset.htm
Attachments
Add attachment proposed patch, testcase, etc.
Ahmad Saleem
Comment 1 2022-10-16 12:22:03 PDT
This test is now on WPT: https://wpt.fyi/results/xhr/send-content-type-charset.htm?label=experimental&label=master&aligned and Safari Technology Preview 155 passes all tests. Marking this as "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.