[
https://issues.apache.org/jira/browse/THRIFT-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157259#comment-14157259
]
Jens Geyer edited comment on THRIFT-2674 at 10/2/14 9:55 PM:
-------------------------------------------------------------
Not sure if I brought my point across properly: I would happily support the
suffix, if asked. They exist for a reason. Even more, if such a simple action
like picking the right MIME type suffix enables us to gain advantages like
those you mentioned above. On the other hand I am not so much involved in that
matter that I have developed strong opinions about it, so just $0,02
was (Author: jensg):
Not sure if I brought my point across properly: I would happily support the
suffix, if asked. They exist for a reason. Even more, if such a simple action
like picking the right MIME type suffix enables us to gain advantages like
those you mentioned above.
> 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)
