Kyle Smith created THRIFT-4848:
----------------------------------
Summary: 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
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)