code 400, message Bad request syntax ('\x88\x80\xa32\xc9\x98')
Asked Answered
U

2

7

noVNC websocket log shows above message on an authentication event. The authentication is always failing and noVNC is reporting subject error.

Some times the error comes as code 400, message Bad HTTP/0.9 request type ('\x88\x8fR\x80\x19\x98QhM\xf9')

Is ('\x88\x80\xa32\xc9\x98') an ASCII or UTF-8 ? How to read and understand this message ?

Background : CentOS 5 / Python 2.4.3 / noVNC

Ultima answered 4/12, 2015 at 15:8 Comment(5)
try to see this github.com/kanaka/noVNC/issues/422Garvey
Removing path as websockify does not help. The output remains same.Ultima
It seems this can be safely ignored for noVNC case. I was able to get noVNC working despite having this message & this had nothing to do with authentication. Thanks.Ultima
have a look at this post: arkilis.me/?p=539Nephoscope
github.com/valor-software/ng2-file-upload/issues/1029Warfourd
C
4

For those that stumbled to this page...and you are just running a vanilla tensorboard setup, first verify your url starts with "http://" as oppose to "https://"!

The message below is what i got when i attempted to access tensorboard (http) with https:

code 400, message Bad request version ('\x1a\x1a\x13\x01\x13 ...

Chili answered 24/10, 2022 at 13:54 Comment(0)
M
1

It seems this was a bug on websockify's side. It is fixed now, but they didn't make a release that includes the fix, so you have to use the master branch if you want to benefit from it.

Alternatively, you could just add the relevant line from that pull request to the file websockify/websocket.py.

Ml answered 22/8, 2017 at 14:23 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.