dotnet / dotnet/aspnetcore

SignalR js client doesn't fallback to LongPolling when it fails to connect with server side events

Open
#20,500 13 comments 1 reaction 0 assignees View on GitHub
affected-few area-signalr enhancement severity-minor
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

### Describe the bug
SignalR js client doesn't fallback to LongPolling when it fails to connect with server side events.

### To Reproduce
Setup the scenario described in #20498

The following is logged and it doesn't try to connect with LongPolling after SSE fails.
![image](https://user-images.githubusercontent.com/3148297/78364353-99556280-75bd-11ea-8d6d-13b68f1f746d.png)

These are the network calls made.
![image](https://user-images.githubusercontent.com/3148297/78364458-c30e8980-75bd-11ea-8ccb-bab97cd70e22.png)

### Second scenario
I also had the issue in another scenario where I think a local firewall is messing with the connection where it won't fallback to LongPolling.
There this is logged.
![image](https://user-images.githubusercontent.com/3148297/78364756-49c36680-75be-11ea-86aa-44b5c6f7ae9a.png)

And these network calls are made.
![image](https://user-images.githubusercontent.com/3148297/78365258-1fbe7400-75bf-11ea-80c7-ad50f7c5b661.png)

When I use an old version of ASP.Net SignalR on the same server the fallback to LongPolling works as expected.
![image](https://user-images.githubusercontent.com/3148297/78364986-b0e11b00-75be-11ea-9c74-23c184ebfde3.png)

### Further technical details
- ASP.NET Core version 3.1

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.