You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/06 18:14:41 UTC

[jira] [Commented] (THRIFT-4018) Ruby server can corrupt connections by putting ApplicationException in the middle of a response

    [ https://issues.apache.org/jira/browse/THRIFT-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854476#comment-15854476 ] 

ASF GitHub Bot commented on THRIFT-4018:
----------------------------------------

Github user jeking3 commented on the issue:

    https://github.com/apache/thrift/pull/1148
  
    Would you be able to rebase this on the current master and push?  This would kick a new build, and I would like to see it pass before merging anything.


> Ruby server can corrupt connections by putting ApplicationException in the middle of a response
> -----------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-4018
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4018
>             Project: Thrift
>          Issue Type: Bug
>          Components: Ruby - Library
>    Affects Versions: 0.9.3
>            Reporter: Dan Bravender
>
> # Have a client make a call to a thrift server method that returns an invalid value for an enum
> # Have the client make another call to the same method that returns an invalid value for an enum
> *Expected*: Thrift server responds with an ApplicationException for both calls
> *Actual*: The thrift server responds with ApplicationException for the first call but then further calls can't be parsed by the client because there is unexpected data that the client cannot parse 
> I discovered this while writing a test case for THRIFT-3781 though it is the opposite problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)