Specifying the hubs url for a connection url should fail #1707

davidfowl opened this Issue Mar 17, 2013 · 1 comment


None yet
4 participants

davidfowl commented Mar 17, 2013

See #1703 for some of the confusion caused by this.

People don't understand the difference between /signalr and /signalr/hubs (the latter being the javascript proxy). The bigger issue is that sometimes specifying /signalr/hubs as the url might work since the server only does an EndsWith check.

Since this issue is very common, we should make the client fail if the connection url ends with /hubs on Start.

Change the .NET client and the JS client.

@ghost ghost assigned abnanda1 Mar 17, 2013

@ghost ghost assigned halter73 Mar 27, 2013

This comment has been minimized.

Show comment Hide comment

Xiaohongt Apr 1, 2013


verified we append "/poll" to polling


Xiaohongt commented Apr 1, 2013

verified we append "/poll" to polling

@Xiaohongt Xiaohongt closed this Apr 1, 2013

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