WebSocketBadStatusException: Handshake status 200 OK about signalrcore HOT 6 CLOSED

only websockets for now.

I think I found my misstake. My problem has palce on my company network and application infrastucture. SignalR have all transport types turn on by default. I this case I got "Handshake status 200 OK". When I set transport type only to WebSockets I got "Handshake status 404 Not Found". My thesis is our IIS is not configured to allow websocket communication.
I'll write to our administratiors to set this feature in IIS. I'll write when I have some new informations.

from signalrcore.

Hi,

This issue could be related with that?
https://stackoverflow.com/questions/45840855/websocket-handshake-status-200-exception

from signalrcore.

Hi,

This issue could be related with that?
https://stackoverflow.com/questions/45840855/websocket-handshake-status-200-exception

My site is over HTTPS so WSS protocol for web sockets connection is right. Do your library use only websockets or is there possiblility to connect over long pooling?

from signalrcore.

only websockets for now.

from signalrcore.

In my case "Handshake status 200 OK" is when they use wrong transport type. "Handshake status 404 Not found" is when websockets communication is not allowed on server side.

from signalrcore.

only websockets for now.

I closed this issue. It would be great to have support for long pooling and SSE in future. Please put somewhere in docs information about supporting WS only (I didn't found it there).

from signalrcore.