[
https://issues.apache.org/jira/browse/CXF-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-4504.
-----------------------------------
Resolution: Not A Problem
Assignee: Sergey Beryozkin
Different media types may have parameters with or without quotes. It is up to
the processor of a given media type to understand how to treat given
parameters, stripping the quotes at MediaType level will lead to MediaType
instance failing to reproduce the original String value
> MediaTypeHeaderProvider stores parameter values of Content-Type header as
> quoted strings if they're quoted in the header
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-4504
> URL: https://issues.apache.org/jira/browse/CXF-4504
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 2.3.1
> Reporter: Michal Gajdos
> Assignee: Sergey Beryozkin
>
> If parameters of {{Content-Type}} header are quoted (e.g. boundary) then the
> whole quoted string is stored as a parameter value in {{MediaType}} instance.
> Example:
> Parsing the following header:
> {{code}}
> Content-Type: multipart/form-data;boundary="MrmiiyyJEqRYcIJyun5tMVIz70NuQ_nfD"
> {{code}}
> causes the {{boundary}} parameter in {{MediaType}} instance to have value
> {{"MrmiiyyJEqRYcIJyun5tMVIz70NuQ_nfD"}} instead of
> {{MrmiiyyJEqRYcIJyun5tMVIz70NuQ_nfD}}.
> This is a problem when an application with both CXF and Jersey is deployed on
> a server. If {{RuntimeDelegate}} from CXF is used in Jersey application
> {{MediaTypeHeaderProvider}} may create a {{MediaType}} instance (when working
> with multipart) Jersey is not able to work with (because of the quoted
> boundary value).
> For more details see: http://java.net/jira/browse/JERSEY-1420
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
