[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516942#comment-14516942
]
ASF GitHub Bot commented on THRIFT-2674:
----------------------------------------
GitHub user stigsb opened a pull request:
https://github.com/apache/thrift/pull/468
JavaScript: set Accept: and Content-Type: headers in request
This is an updated patch for THRIFT-2674.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stigsb/thrift THRIFT-2674
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/468.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #468
----
commit 7a32f328f4d03a908e3d6fedd20d8ccfb940a9cb
Author: Stig Bakken <s...@zedge.net>
Date: 2014-08-21T19:18:08Z
JavaScript: set Accept: and Content-Type: headers in request
----
> 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)
