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

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

--- Comment #15 from Julian Reschke <julian.reschke@gmx.de> 2012-04-12 09:35:04 UTC ---
(In reply to comment #14)
> I'm not assuming that. I'm just saying I don't want to leave edge cases
> undefined. We could also make this about the first or last charset parameter,
> as I've indicated.

"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."

To make this decision, a UA will have to run the field value through a parser,
otherwise it will not know about individual parameters.

> Throwing an exception instead (where? for what method?) is not at all a simpler
> solution nor a solution that is going to work.

For setRequestHeader() if possible, otherwise for send().

It is simpler as it doesn't require the UA to have a parser for broken field
values.

Also, when you claim "is not going to work" it would be awesome if you could
explain why.

-- 
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 09:35:08 UTC