Open MarcoWagner opened 1 year ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I am using SignalR-Client-Cpp from inside a corporate network to connect to a public (online) signalR hub. The connection goes through a WAF which is incompatible to websockets.
Describe the solution you'd like
Automatic fallback to use Long Polling Transport when the
Upgrade
to Websockets is not possible.Additional context
No response