Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-4018

Ruby server can corrupt connections by putting ApplicationException in the middle of a response

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.9.3
    • None
    • Ruby - Library
    • None

    Description

      1. Have a client make a call to a thrift server method that returns an invalid value for an enum
      2. 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            dbravender Dan Bravender

            Dates

              Created:
              Updated:

              Slack

                Issue deployment