You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2016/06/27 21:03:17 UTC
[jira] [Comment Edited] (CXF-6954) JAXRSUtils.parseMediaTypes does
not support semicolons
[ https://issues.apache.org/jira/browse/CXF-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351806#comment-15351806 ]
Sergey Beryozkin edited comment on CXF-6954 at 6/27/16 9:02 PM:
----------------------------------------------------------------
Note, one can always use pre-matching ContainerRequestFilter to modify various request properties to adapt the clients
was (Author: sergey_beryozkin):
Note, once can always use pre-matching ContainerRequestFilter to modify various request properties to adapt the clients
> 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)