Open csaavedra opened 5 years ago
Hi there, I'm trying to test the conformance of the client I wrote IXWebSocket because the server my client is hitting (python websockets) is giving me a very similar zlib error (invalid distance too far back).
https://github.com/aaugustin/websockets/issues/665
For what it's worth here is how my client behave when I try to hit the 'case 322' == your failing case.
$ ws connect -d 'ws://localhost:9001/runCase?case=322&agent=ixwebsocket'
Type Ctrl-D to exit prompt...
Connecting to url: ws://localhost:9001/runCase?case=322&agent=ixwebsocket
> ws_connect: connected
Uri: /runCase?case=322&agent=ixwebsocket
Handshake Headers:
Connection: Upgrade
Sec-WebSocket-Accept: KqiDNPfJQWMT5QBWf40ax2A1teY=
Sec-WebSocket-Extensions: permessage-deflate; server_max_window_bits=15
Server: AutobahnTestSuite/0.8.0-0.10.9
Upgrade: WebSocket
X-Powered-By: AutobahnPython/0.10.9
Received 18 bytes
ws_connect: received message: %PDF-1.2
%?쏢
6
It looks like the client should hit a 'url', receive a message, and when the connection is closed (by the server ?), try to hit the 'next url' ?
Actually I figured out how to work with autobahn (generate url with test-case id inside them, and have a client just echo the message sent by the server until it is disconnected, and then move on to the next test case).
I found out this to be an actual corruption on the client-side code, fixing the corruption made the test pass and this exception is gone. I suppose that the exception was just zlib or similar having trouble to deflate the corrupted data. Feel free to close if you agree with this.
This test happens to fail for the client I am testing it with (libsoup), but in the server-side I see this exception which I now wonder is expected at all. This is with the
autobahn/latest
Docker image. Reporting in case it's useful:The .json output for the test: