Secure WebSockets

[Chris]

Hello Everybody,

I apologize for my ignorant question, but I am having a lot of trouble
with this.

I am working on building a WebSocket server. It is currently
implemented as a fairly standard inheritance from WebSocketHandler. It
works well, and handles the connection perfectly. However, when I
attempt to connect using wss (secure websockets), it doesn't function
properly. The server shows no reaction, with none of the "open" or
"on_close" or "on_error" methods being called on the handler. The
client never registers as having an open connection (never runs the
"on_open" method in javascript), but does run the "on_close" method if
the server if halted during this process.

What am I missing? I have tried, without success, to find some
documentation of Secure Websockets with Tornado. It seems to me that
the server is receiving the connection, but does nothing without
(including not rejecting or closing it).

Can anyone help me with this issue?

Thank you very much for your time,

---Chris

[Kevin Constantine]

In my case it ended up being that none of my browsers were prompting me to accept a self-signed certificate. 

I did a little write-up on this issue here:
http://kconstan.tumblr.com/post/36603279595/browsers-dont-prompt-for-self-signed-certificates-with

Hope that helps!

-kevin

On Fri, Dec 28, 2012 at 1:03 AM, Hermann Yung <hong.kon...@gmail.com> wrote:

I also want to know this too!

Kevin Constantine於 2012年11月17日星期六UTC+8上午8時47分38秒寫道：

Chris, did you ever find the answer to this question?  I'm running into a similar issue, and it feels like I'm just missing something stupid.

-kevin