-
Notifications
You must be signed in to change notification settings - Fork 218
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
Upgrade Tyrus WebSocket client library (used in Socket Mode client ) to v2 #972
Comments
HI @gillbates, thanks for writing in! We are planning to upgrade to Tyrus v2 in the next major version: #919 That being said, this SDK's v2 won't come in the short term (at least, we are not planning to work on it this year). If this issue is urgent for you, please consider implementing your own |
Hi @seratch thx for the clarify. Currently there are lot of needs for proxy support for both http api and websockets. |
If I understand correctly, Tyrus v2 does not support SOCKS proxies out-of-the-box too. The logging part is still the same: https://github.com/eclipse-ee4j/tyrus/blob/2.0.2/containers/grizzly-client/src/main/java/org/glassfish/tyrus/container/grizzly/client/GrizzlyClientSocket.java#L594-L598 Currently, this SDK supports only HTTP proxy and many of the use cases that we are aware have been covered by that. That being said, when any of the underlying WebSocket libraries support SOCKS5 proxies, we can provide tools for the use cases. As for the oldness of Tyrus v1.17, indeed the version was released in 2020. The Tyrus team released v1.18 a few months ago but this project haven't upgraded the depending version yet. We will specify v1.18 instead since the next release. Also, if we see more demands on Tyrus v2 support in prior to this SDK's v2 release, we may consider adding a separate optional module for it (like we do for Jetty v11 supports). https://search.maven.org/artifact/org.glassfish.tyrus/tyrus-client Thanks again for sharing this and it'd be appreciated if you could understand this. |
Hai , i am connect websocket throw tyrus-standalone-client version 1.19 for chrome version 109.0.5414.119-1 it working fine ,but now chrome version is upgraded to 112 .i can't able to connect to browser . so i used tyrus-standalone-client version 2.1.3 it throws a handshake error. why ?what is the reason? |
(Describe your issue and goal here)
Reproducible in:
The Slack SDK version
Java Runtime version
OS info
Steps to reproduce:
Expected result:
can we support socks5 proxy for both slack http api and websocket api
Actual result:
The text was updated successfully, but these errors were encountered: