1
Vote

Content negotiation ignores charset media type parameter in Accept header

description

I would expect that setting the charset media type parameter in the accept header would cause that charset to be selected. However, content negotiation appears to consider only the Accept-Charset header and not the charset media type parameter within the Accept header.

Note that Apache appears to honor the charset media type parameter within the Accept header:
http://httpd.apache.org/docs/current/content-negotiation.html
"Browser indicates preference with the Accept-Charset header field. Each item can have a quality factor. Variants can indicate a charset as a parameter of the media type. "

Also, some one MS OData implementation consider it as well, even giving it priority over the Accept-Charset header. (See ODataMessageWriterSettings.SetContentType and ODataUtils.SetHeadersForPayload.)

comments

HenrikN wrote Oct 17, 2012 at 5:54 PM

We opted not to do that as the HTTP spec is silent on what it means to indicate a charset parameter on a media type value within an accept header. The only place it talks about charset negotiation is as part of the Accept-Charset header field.

We likely won't change the current behavior but if you feel strongly enough to generate a pull request then we certainly would consider it :)

Sign in to add a comment or to set email notifications