Skip to content
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

FP11 SecureSocket support & socket connection timeout param #122

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

TilmanGriesel
Copy link

We encountered some SSL/TLS connection problems with f5 load balancers and SSL offloading. We fixed this with a implementation of the new SecureSocket provided by adobe. Another problem was the long connection timeout (20s). We think we give this back to the community, thanks for the great library.

Tilman Griesel added 2 commits August 28, 2012 17:34
- added an option to use the new SecureSocket class to build on SSL/TLS web socket connections
@gimite
Copy link
Owner

gimite commented Aug 31, 2012

I heard that using SecureSocket causes other issues. See #68 . Can you explain detail of the issue you encountered?

Because native WebSocket in Web browsers doesn't support timeout specification, I won't add it to web-socket-js. You can still implement timeout in your application by checking if "open" event fires in X seconds.

@TilmanGriesel
Copy link
Author

Thanks for the information and response. We encountered, that the server never respond to our request header. I don't know exactly why this is happen. After a lot of investigation i wrote my own Web-socket implementation prototype. I never got valid connections with the hurlant lib. After a try with the native SecureSocket class the connection was established immediately. I think it is a good way to provide multiple methods to connect to the server.

@gimite
Copy link
Owner

gimite commented Aug 31, 2012

I see, thanks for the explanation. What WebSocket server do you use? Or did you write your own?

Until the exact cause is clear or other people report the same issue, I want to pend it for now, because it's not clear whether it's general issue or specific to your environment at this moment.

@TilmanGriesel
Copy link
Author

The WebSocket Server was Slanger [https://github.com/stevegraham/slanger] with an f5 big-ip load balancer [http://www.f5.com/products/big-ip]. The SSL connection was provided by the f5 (ssl offloading)[http://www.f5.com/glossary/ssl-offloading.html].
With other wss servers i never experienced this problem. Only on our production environment with the f5 this problem exists.

btw: Your web-socket-ruby implementation connects to the f5 wss without any problems.
(this is the reason why I think something is broken in the hurlant lib)

@leefj
Copy link

leefj commented Dec 21, 2016

i use Netty and SecureSocket in my App.
it works on iOS ,but not work on android . on android the SecureSocket.serverCertificateStatus value is invalid .
does any body know how to solve this problem?
and shat "user-permission" should config ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants