[infinispan-issues] [JBoss JIRA] (ISPN-2819) REST server ignores client header Accept-Charset

[Gustavo Fernandes (JIRA)]

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

Gustavo Fernandes commented on ISPN-2819:
-----------------------------------------

The REST server supports the charset in the client's originated {{Accept}} header. e.g. https://github.com/gustavonalle/infinispan/blob/a39fbd0c97b6e121a6951d8558aac715503002f8/server/rest/src/test/java/org/infinispan/rest/BaseRestOperationsTest.java#L512, supporting also the {{Accept-Charset}} seems redundant to me.



> REST server ignores client header Accept-Charset
> ------------------------------------------------
>
>                 Key: ISPN-2819
>                 URL: https://issues.jboss.org/browse/ISPN-2819
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Remote Protocols
>    Affects Versions: 5.2.1.Final
>            Reporter: Dan Berindei
>            Assignee: Galder Zamarreño
>            Priority: Minor
>
> In a HTTP GET request, the client can specify an {{Accept-Charset}} header. The REST server will ignore it, and it will always send the response with the original PUT/POST request's charset.
> I think the server should make an effort to transform the value data from the PUT charset to the GET charset. At the moment we don't even parse the PUT charset, we just store the {{Content-Type}} header.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)