[infinispan-issues] [JBoss JIRA] (ISPN-2820) POST request with multipart/form-data encoding stores wrong content type

[Galder Zamarreño (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781327#comment-12781327 ] 

Galder Zamarreño commented on ISPN-2820:
----------------------------------------

[~dan.berindei], not sure how this should be handled, and it'd argue that it might be a new feature... so moving it to 6.0.


                
> POST request with multipart/form-data encoding stores wrong content type
> ------------------------------------------------------------------------
>
>                 Key: ISPN-2820
>                 URL: https://issues.jboss.org/browse/ISPN-2820
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Remote protocols
>    Affects Versions: 5.2.1.Final
>            Reporter: Dan Berindei
>            Assignee: Galder Zamarreño
>             Fix For: 5.3.0.Final
>
>
> The REST server uses the {{Content-Type}} header of the POST request to determine the content type of the stored entry. But with {{Content-Type: multipart/form-data}}, each parameter can have its own content type (and {{multipart/form-data}} is definitely not any parameter's content type).
> This seems to be the way to do get the content type of each parameter: http://www.mkyong.com/webservices/jax-rs/file-upload-example-in-resteasy/

--
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