[
https://issues.apache.org/jira/browse/SHINDIG-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163800#comment-13163800
]
Randy Hudson commented on SHINDIG-1181:
---------------------------------------
Paul, in our case, it doesn't matter that shindig's caching support currently
doesn't respect content negotiation for different forms of the same resource.
Our web clients *always* use Accept: "text/json", while our non-web clients use
something else. So allowing the Accept header under the assumption that it is
always the same value would be a start. Supporting multiple values would be
extra credit.
> Cannot use accept headers with makeRequest
> ------------------------------------------
>
> Key: SHINDIG-1181
> URL: https://issues.apache.org/jira/browse/SHINDIG-1181
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 1.1-BETA3
> Reporter: Adam Archer
> Fix For: 1.1-BETA4
>
> Attachments: shindig-1181.patch
>
>
> MakeRequestHandler blocks several headers that can be sent in a makeRequest
> call from the client (using gadgets.io.RequestParameters.HEADERS). One of the
> blocked headers is "accept" which is preventing us from consuming our REST
> services as JSON since they return xml by default unless the appropriate
> header is used.
> I have tried removing "ACCEPT" from MakeRequestHandler.BAD_HEADERS locally.
> This fixes the problem and I haven't noticed any adverse side effects.
> See the mailing list thread: "MakeRequestHandler.BAD_HEADERS... is killing
> our REST Service calls"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
