You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2021/03/18 15:57:00 UTC

[jira] [Resolved] (THRIFT-5373) HTTP status in case of Protocol/Transport exceptions

     [ https://issues.apache.org/jira/browse/THRIFT-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer resolved THRIFT-5373.
--------------------------------
    Fix Version/s: 0.15.0
       Resolution: Fixed

> 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
>             Fix For: 0.15.0
>
>         Attachments: 0001-THRIFT-5373-HTTP-status-in-case-of-Protocol-Transpor.patch
>
>
> 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. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)