[THRIFT-5373] HTTP status in case of Protocol/Transport exceptions

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15.0
• Component/s: netstd - Library
• Patch Info: Patch Available
• Assignee: Jens Geyer
• Reporter: Jens Geyer
• Created: 18/Mar/21 15:48
• Updated: 11/Sep/21 12:30
• Resolved: 18/Mar/21 15:56

Description

The THttpServerTransport already handles TTransportExceptions that occur during the "message receive" phase and delivers a HTTP 500 (internal server error) when no other response has been generated so far (instead of delivering the default HTTP 200 OK along with an empty message).

What is currently not handled is TProtocolExceptions (happens i.e. when a required field is missing). So the goal of the ticket is to a) handle these errors as well and b) return a HTTP 400 (bad request) to indicate the error to the client.