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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[馃悰 Bug]: [Ruby][C#] Exception when using wss protocol in se:cdp #10017
Comments
@shashikdm, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
After troubleshooting the issue, please add the Thank you! |
After some digging around ruby WebSockets, I found that it shows the timeout behaviour when connecting with any
Above script gets stuck at
Please note that the host in above script (hidden-earth-77678.herokuapp.com) is a simple WebSocket server in node js explained here: https://devcenter.heroku.com/articles/node-websockets#option-1-websocket. |
Observed same behaviour with C# client library.
Stacktrace:
|
This should be fixed in 4.1, please let us know if it is not. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
I'm using a WebSocket proxy between Selenium Jar and client script for the BiDi connection. When I use
ws
protocol, i.e."se:cdp": "ws://<proxy>/session/<sessionId>/se/cdp"
, the example script works as expected. However, if I usewss
protocol, i.e."se:cdp": "wss://<proxy>/session/<sessionId>/se/cdp"
, I get a runtime exception. This happens with ruby and C# client only. It works fine Java client.How can we reproduce the issue?
Relevant log output
Operating System
macOS Monterey
Selenium version
Ruby 4.0.3
What are the browser(s) and version(s) where you see this issue?
Chrome 94
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 94.0.4606.61
Are you using Selenium Grid?
4.0.0-rc-1
The text was updated successfully, but these errors were encountered: