-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Server-side exception with test 12.2.1 #99
Comments
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). python-websockets/websockets#665 For what it's worth here is how my client behave when I try to hit the 'case 322' == your failing case.
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:
The text was updated successfully, but these errors were encountered: