I am trying to use a Cookie along with ssl_session_id to identify
connections. This seems to work fine in Chrome and Firefox, but Safari
looks like it uses a different ssl_session_id when it makes a
websocket connection. Is there something else I can use to uniquely
tie the cookie to a connection?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx