Hi Christian,
I’m not aware of any implementation using Accept-Charset to influence the matching algorithm. Hopefully others can comment on this thread too.
— Santiago
Hi Santiago,
I agree that this issue needs more investigation. It looks like there are good argument for both preferring "Accept-Charset" and "Accept" with a charset parameter.
However, it is very weird that JAX-RS currently completely ignores "Accept-Charset" in the default case (not using Request.selectVariant()) although it is defined in RFC2616.
To sum up the facts: - RFC2616 explicitly defines "Accept-Charset" as the way for the client to request a preference for the charset.
- There are different opinions about whether the "charset" media type parameter is allowed with the "Accept" header or not.
Does anyone know how the different JAX-RS implementations handle the "Accept-Charset" parameter? Is any implementation actually using it for something other than Request.selectVariant()?
Christian
Christian,
I see a number of somewhat inconclusive discussions about this issue [1]. I don’t particularly prefer one approach over the other, but if we are going to make a change, we should be certain about it. Moreover, switching to Accept-Charset is likely to introduce a backward compatibility issue for us, which reinforces even more the certainty argument.
Looks like this may require a bit more investigation.
— Santiago
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
--
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
|