zaphoyd/websocketpp — Issue #61: Braindead safari (mailformed http) exits the server loop
Author: Sfinx
Created: 2012-02-02 20:45:43+00:00
State: open

Hello,

I'm trying to write the websocket server that will never exits (24x7), so I'm using the chrome/firefox at client side. I do not need the safari support at all, but when some apple user opens the url - it blows up the server loop when the access was by http protocol. (https connection gives the protocol == 0). So I've got something like :

........
2012-02-02T22:31:41 [16] Missing Key3
2012-02-02T22:31:41 [16] Handshake ended with HTTP error: 400
........

This is because of http::exception that exits all the server instead of gracefull close of the invalid connection. How this problem can be avoided/fixed ? Sure the browser check can be done at HTML/JS level but it is unreliable - more robust is to make this at the server side.

Thanks