[
https://issues.apache.org/jira/browse/CXF-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351804#comment-15351804
]
Sergey Beryozkin commented on CXF-6954:
---------------------------------------
Well, how would a runtime know where the next media type starts ? Especially if
more than one parameter for a given media type is available. Can you point me
please to the relevant spec text ?
> JAXRSUtils.parseMediaTypes does not support semicolons
> ------------------------------------------------------
>
> Key: CXF-6954
> URL: https://issues.apache.org/jira/browse/CXF-6954
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.1.6
> Reporter: Ryan Diehl
>
> We have a client application sending an Accept header in the following
> format:
> Accept=*/*; q=0.5; application/json
> The HTTP spec seems to allow for both comma and semicolon as separator
> characters in this use case. When a client sends this request, it is not
> split up, and results in an unsupported media type and an HTTP 406 error.
> Fortunately in our case, we are in control of the client, so we can modify
> the accept header. However, this may not always be the case for us, so I am
> logging this ticket in hopes of getting clarification on the expected
> behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
