[
https://issues.apache.org/jira/browse/THRIFT-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer updated THRIFT-5373:
-------------------------------
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.
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.
was:
The THttpServerTransport already handles TTransportExceptions and delivers a
HTTP 500 (internal server error) in such a case.
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.
> HTTP status in case of Protocol/Transport exceptions
> ----------------------------------------------------
>
> Key: THRIFT-5373
> URL: https://issues.apache.org/jira/browse/THRIFT-5373
> Project: Thrift
> Issue Type: Improvement
> Components: netstd - Library
> Reporter: Jens Geyer
> Assignee: Jens Geyer
> Priority: Major
>
> 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.
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
