Java Script client pings wrong server in a cross domain environment.

[Alsc0]

I have two web applications where one application is a typical web site having SignalR Java Script client. The other one is the SignalR server application, where Java Script client connects to.

When I open the page with the SignarR client and leave it open for some time it sends ping request to the wrong server. I have attached the screen grab that have all the details.

It seems that there is no functional impact, other that pinging the wrong server and getting 404s.

Steps to reproduce:

1. Create two empty web applications in VS2012.
2. Add SignalR Javascript Client to one application, and a page that connects to other application.
3. Add SignalR Server components to the other application (I'm using PersistentConnection but I don't think this changes anything).
4. Configure both web application in IIS (I'm using Windows 8, both applications having their own host name registered in etc file. Though the same issue was noticed when using IIS Express, using different ports on localhost).
5. Opent the page with SignalR Javascript Client in the browser ( I'm using Chrome Version 30.0.1599.101 m) and leave it for some time (~2 min maybe) with Console opened.

Expected:
I guess, all /ping?=[number] should go to web application that has SignalR Server components.

Actual:
/ping?=[number] requests go to web application that has SignalR Java Script client that end up with 404 (Not Found) error.

This issue was observed on SignarR 2.0 and on candidate release as well.

[davidfowl]

Known issue already that's already fixed for the upcoming releases (2.0.1 and 1.1.5) #2569

[Alsc0]

Hi everyone,

I still have this issue.

On the first server I have SignalR JavaScript Client 2.0.1. On the second full 2.0.1 SignalR (.Net Client, Core, JavaScript Client etc.).

The same happens as above but this time I changed the first server to respond with 302 to NotFound page. And things got worse as SignalR client closes the connection. Please see the image.

I'm using persistent connections.

Can you please share your thoughts?

Thank you.

[davidfowl]

@Alex-Endava Check out the release notes. This change is NOT is any realize as yet. Fixed just means it's fixed in the development branch not in any public release. If you want the fix before a release then you can use the nightly builds on the myget feed https://www.myget.org/F/aspnetwebstacknightly/. Otherwise you need to either grab the source yourself or wait for a release.