After some research into a problem with websockets through fabio when using IE10, I have discovered that IE10 sends the following header:
Upgrade: Websocket
It seems fabio i not treating this header value wrong because of the casing.
I have a SignalR application behind fabio, and I get an error (400), and SignalR falls back on longpolling. However if I edit the request for initiating the websocket connection in fiddler, and change the header to the below it seems to work (the request gets a 101 back not a 400) (notice the casing).
Upgrade: websocket
After some research into a problem with websockets through fabio when using IE10, I have discovered that IE10 sends the following header:
Upgrade: Websocket
It seems fabio i not treating this header value wrong because of the casing.
I have a SignalR application behind fabio, and I get an error (400), and SignalR falls back on longpolling. However if I edit the request for initiating the websocket connection in fiddler, and change the header to the below it seems to work (the request gets a 101 back not a 400) (notice the casing).
Upgrade: websocket