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

TProtocolException: Bad version in readMessageBegin when using XHR client with C++ server

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 0.13.0
    • None
    • Node.js - Library
    • None

    Description

      I'm getting a "TProtocolException: Bad version in readMessageBegin" in the web browser when running an XHR client with binary protocol on a C++ server. The issue comes as soon as I call a method with return value that returns for example an int32_t.

      This is tested with latest thrift from master.

      The Nodejs Http client works successfully with binary protocol, so the issue seems to be related to the XHR connection or XHR client.

       

      Is this a bug or am I doing something wrong? I've found this report in various places on the internet, in combination with Cassandra. It seems this happened for Cassandra in the past, but as far as I could see, it was resolved by switching to the compact protocol.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              emmenlau Mario Emmenlauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h
                  1h