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

["Jens Geyer (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/THRIFT-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer reassigned THRIFT-4987:
----------------------------------

    Assignee: Carel

> 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
>            Assignee: Carel
>            Priority: Major
>             Fix For: 0.23.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> 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.20.10#820010)