-
Notifications
You must be signed in to change notification settings - Fork 112
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
WebSocketBadStatusException raised when connecting to webSocketDebuggerUrl in Chrome 108+ #59
Comments
Seems to be related to Chrome checking the Origin of the incoming request. The recommended fix seems to be to suppress the header entirely: https://bugs.chromium.org/p/chromium/issues/detail?id=1422444#c5 I added an extra kwarg Line 208 in c6c755b
|
I tried it and that worked! Thanks and good job! 💖 |
This fix worked. Can you raise the PR for this? |
See fate0/pychrome#59 With chrome 108+, this exception is raised: websocket._exceptions.WebSocketBadStatusException: Handshake status 403 Forbidden On github CI, chrome 112.0.5615.121 is currently installed and leads to that crash.
See fate0/pychrome#59 With chrome 108+, this exception is raised: websocket._exceptions.WebSocketBadStatusException: Handshake status 403 Forbidden On github CI, chrome 112.0.5615.121 is currently installed and leads to that crash.
See fate0/pychrome#59 With chrome 108+, this exception is raised: websocket._exceptions.WebSocketBadStatusException: Handshake status 403 Forbidden On github CI, chrome 112.0.5615.121 is currently installed and leads to that crash.
version(0.2.4) I'm using has this independent of any port I use. chrome version: 117.0.5938.63 |
start chrome with one of
chrome will print this to stderr
see also |
When using PyChrome to connect to a tab's "webSocketDebuggerUrl" in Chrome 108 or newer, the following error is raised: "websocket._exceptions.WebSocketBadStatusException: Handshake status 403 Forbidden".
The text was updated successfully, but these errors were encountered: