[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520677#comment-14520677
]
Henrique Mendonça commented on THRIFT-2674:
-------------------------------------------
Hi guys,
THRIFT-2756 is now resolved, but from my understanding the content type has to
be chosen by the TProtocol. Either by setting it directly on the Transport or
sending a parameter on every request. (Both a bit of a work around the
architecture. How do the other libraries solve this?)
My first question here is actually if we should commit this as it is for now,
as JQ already fixes json, or wait for a more complete solution?
Cheers,
Henrique
> 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
> Attachments: js-type.diff
>
>
> 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.3.4#6332)
