[THRIFT-4848] Add ability to set Content-Type,Accept headers in HTTP client

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Component/s: netstd - Library
• Assignee: Kyle Smith
• Reporter: Kyle Smith
• Created: 15/Apr/19 14:01
• Updated: 16/Oct/19 22:26
• Resolved: 14/Jun/19 20:44

Description

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.

Issue Links

• links to: GitHub Pull Request #1801