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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.13.0
• Component/s: Node.js - Library
• Assignee: Unassigned
• Reporter: Mario Emmenlauer
• Created: 31/Oct/19 15:42
• Updated: 22/Aug/22 20:25

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.

Issue Links

• links to: GitHub Pull Request #2157