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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16303

--- Comment #7 from Julian Reschke <julian.reschke@gmx.de> 2012-04-12 08:44:59 UTC ---
(In reply to comment #6)
> What do you mean by "it" and what would removing "it" mean? I don't really care
> that much what we do here, but I disagree that this is over-specification.
> Multiple charset parameters is a legitimate situation that can come up and
> implementors need to know what to do.

things the spec says (last time I checked):

a) rewrite Content-Type request header field, because XHR *will* use UTF-8

b) if original charset matched UTF-8, preserve it's exact representation (so
don't rewrite "Utf-8" to "UTF-8")

c) in addition, do that for all additional charset params

So this is an edge case of an edge case of an edge case.

Optimally, we can get rid of all of this; just declare that if the sender
doesn't specify UTF-8, it's his problem (resulting in an inconsistent request).

b) seems to be a workaround for one broken server seen in the past. Maybe it
was fixed?

c) over-specifies b) for the a broken input. Nobody implements it. Why do you
care about this edge case in the first place?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 12 April 2012 08:45:07 UTC