W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

[Bug 16303] New: meaning of "all" charset parameters of content-type header

From: <bugzilla@jessica.w3.org>
Date: Sat, 10 Mar 2012 07:06:27 +0000
To: public-webapps@w3.org
Message-ID: <bug-16303-2927@http.www.w3.org/Bugs/Public/>

           Summary: meaning of "all" charset parameters of content-type
           Product: WebAppsWG
           Version: unspecified
          Platform: All
               URL: http://dvcs.w3.org/hg/xhr/raw-file/8d4e9ccfdbd4/Overvi
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
        AssignedTo: annevk@opera.com
        ReportedBy: glenn@skynav.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

Section 4.7.6 step 3 states:

"If a Content-Type header is in author request headers and its value is a valid
MIME type that 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
that Content-Type header to encoding."

Questions: what does *all* mean in "set all the charset parameters of that
Content-Type"? could you give a concrete example of a case with more than one
charset parameter in the single media type value of Content-Type?

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 10 March 2012 07:06:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:38 UTC