[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105841#comment-14105841
]
Stig Bakken commented on THRIFT-2674:
-------------------------------------
I think that's a good approach, the most important thing is that it's
consistent across platforms, and that it's RFC-compatible when it comes to
using Accept: and Content-Type: headers.
If "application/thrift" is the default binary encoding, I think appending
either "+json" or "+compact" would be a nice pattern.
> 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)
