[
https://issues.apache.org/jira/browse/THRIFT-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer resolved THRIFT-4848.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.13.0
Committed - thanks!
> Add ability to set Content-Type,Accept headers in HTTP client
> -------------------------------------------------------------
>
> Key: THRIFT-4848
> URL: https://issues.apache.org/jira/browse/THRIFT-4848
> Project: Thrift
> Issue Type: Improvement
> Components: netstd - Library
> Reporter: Kyle Smith
> Assignee: Kyle Smith
> Priority: Minor
> Fix For: 0.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Right now the THttpTransport client does not specify a Content-Type header
> when connecting to an HTTP server, nor does it allow for resetting the Accept
> header. Neither headers can be set using the current CustomHeader properties.
> If these headers could somehow be set based on the protocol being used (like
> in the JavaScript library) then the server instance could use it to properly
> infer what the inbound and outbound protocols should be.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
