[ https://issues.apache.org/jira/browse/THRIFT-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858293#comment-15858293 ]
James E. King, III edited comment on THRIFT-4018 at 2/8/17 6:02 PM: -------------------------------------------------------------------- Based on the title of this ticket, wouldn't it be better to prevent the ruby server from being able to corrupt the stream on the sending side? was (Author: jking3): Based on your title here, wouldn't it be better to prevent the ruby server from being able to corrupt the stream on the sending side? > 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)