[Webkit-unassigned] [Bug 46147] New: XMLHttpRequest: send() does not set Content-Type header correctly if the Content-Type header is set using setRequestHeader()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=46147

           Summary: XMLHttpRequest: send() does not set Content-Type
                    header correctly if the Content-Type header is set
                    using setRequestHeader()
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore JavaScript
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jianli at chromium.org
                CC: ap at webkit.org, fishd at chromium.org,
                    dimich at chromium.org, levin at chromium.org,
                    jianli at chromium.org


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

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.