[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108135#comment-14108135
]
Roger Meier commented on THRIFT-2674:
-------------------------------------
I think we should explicitly mention the protocol:
{noformat}
Content-Type: application/vnd.apache.thrift.binary; # binary
Content-Type: application/vnd.apache.thrift.json; charset=utf-8 # 8-bit text
Content-Type: application/vnd.apache.thrift.compact; # binary
{noformat}
and in the future as soon as we have THeader from fb merged, I see this:
{noformat}
Content-Type: application/vnd.apache.thrift.header;
{noformat}
any concerns?
> JavaScript: declare Accept: and Content-Type: in request
> --------------------------------------------------------
>
> Key: THRIFT-2674
> URL: https://issues.apache.org/jira/browse/THRIFT-2674
> Project: Thrift
> Issue Type: Bug
> Components: JavaScript - Library
> Reporter: Stig Bakken
> Priority: Minor
>
> When a JS client communicates with a backend supporting several encodings,
> knowing which protocol to use is a bit kludgy. This patch tries to fix that
> by always setting the Accept: and Content-Type: request headers to
> "application/json".
--
This message was sent by Atlassian JIRA
(v6.2#6252)
