Open TilmanGriesel opened 12 years ago
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.
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.
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.
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)
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 ?
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.