-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REQUEST: Specify unexpected status code #55
Comments
Indeed, the code is not visible even in verbose mode. Probably should be in Websocat 2.0 |
Any status on this issue? I had the same issue today and it took me some time to find out what's wrong. |
The status is like "waiting for inspiration to resume work on Websocat in general". It may happen if/when I need to advance Websocat for myself for some need. It would be reasonable to rewrite Websocat for a better architecture and newer dependencies, but the lack of real tests makes it tricky to do such rewrite without breakages. And just writing tests is typically boring and I instead switch to other project when I think about it too much... (Also I'm not sure if Websockets in general would have a bright future in future HTTP/3 / QUIC world - one of reasons I have recently added crude SSE support to Websocat). Maybe I can just merge & publish this particular change ahead of big changes, as it looks like there is some popular support for this change. |
Published Next step is to build and upload websocat (probably |
Published a release "v1.6.0" (including pre-built artifacts) with this issue resolved.
|
When the server gives an error, the program indicates:
websocat: WebSocketError: Received unexpected status code
It would be nice if it would specify what the status code actually was, e.g.:
websocat: WebSocketError: Received unexpected status code (404)
The text was updated successfully, but these errors were encountered: