WebSockets transport pings the wrong server URL. #2570

NTaylorMullen opened this Issue Sep 19, 2013 · 1 comment


None yet

2 participants


This is a blatant bug. We special case websockets when creating the URL and we shouldn't.

@NTaylorMullen NTaylorMullen added a commit that referenced this issue Sep 25, 2013
@NTaylorMullen NTaylorMullen Modified the ping server to no longer special case websockets and to …
…use the connection.url.

- Also added a test to verify the fix.


tested on websockets, pingServer is invoked periodically sending a request to "/signalr/ping?connectionData=%5B%7B%22name%22%3A%22hubconnectionapi%22%7D%5D".
Response is "pong" and the deferral is completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment