Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
4.2.0
-
None
-
Unknown
Description
We recently upgraded an application to latest camel stable and got an error report from consumers when submitting a charset parameter in the content type header.
Expected: a request with content-type header `application/xml; charset=utf-8` is correctly validated as part of a rest specification with `.consumes(MediaType.APPLICATION_XML_VALUE)`. We run with bindingmode.off
Actual: fails with 415 MediaType error
What changed?
In commit https://github.com/apache/camel/commit/2ce60e76a5c8496c1468558e0b6d3043c4eb0eac a change in client Request Validation was introduced which defaults validation to return false instead of true.
The charset parameter is part of the Content-Type superset and is not per se a MediaType. We expect setting the correct MediaType would lead to a validation of MediaType and not fail on an additional charset parameter.
Attachments
Attachments
Issue Links
- links to