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

Posted to dev@thrift.apache.org by "Mario Emmenlauer (Jira)" <ji...@apache.org> on 2019/10/31 15:43:00 UTC

[jira] [Created] (THRIFT-4987) TProtocolException: Bad version in readMessageBegin when using XHR client with C++ server

Mario Emmenlauer created THRIFT-4987:
----------------------------------------

             Summary: TProtocolException: Bad version in readMessageBegin when using XHR client with C++ server
                 Key: THRIFT-4987
                 URL: https://issues.apache.org/jira/browse/THRIFT-4987
             Project: Thrift
          Issue Type: Bug
          Components: Node.js - Library
    Affects Versions: 0.13.0
            Reporter: Mario Emmenlauer


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.



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