We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Curious.. Will this library automatically and seamlessly fall back to Long Polling and/or Server-Sent Events when WebSockets are not supported by the server or blocked by a firewall/proxy? It's not clear from the docs https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-7.0#transports, so I just wanted to make sure. TY!
The text was updated successfully, but these errors were encountered:
The client negotiates SSE/WebSockets with the server, but is not able to handle blocked WebSockets.
Sorry, something went wrong.
@tsoeiroecore See #175 for fallback when WebSockets are blocked
No branches or pull requests
Curious.. Will this library automatically and seamlessly fall back to Long Polling and/or Server-Sent Events when WebSockets are not supported by the server or blocked by a firewall/proxy? It's not clear from the docs https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-7.0#transports, so I just wanted to make sure. TY!
The text was updated successfully, but these errors were encountered: