-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
Proxy autodetection doesn't work with websockets/SignalR #214
Comments
There were a call to set a new ProxyDetector from BestHttpSignalRClient.cs:37. What was the new value? A null value effectively disables proxy detection. |
BestHttpSignalRClient.cs:37 is We set it every time before connecting. We also tried doing it only once but didn't make any difference. |
Hmm, i'm going to check it. However, is there a reason you set it manually? The plugin already setting it to a |
Oh, no particular reason, I thought it was necessary, documentation says you need to do it: https://bestdocshub.pages.dev/Shared/proxy/proxy-autodetect/ |
Ohh, i think i copy-pasted from the old documentation for v2, and i might enabled it by default in v3... |
When using websockets (SignalR in my case) the proxy autodetection doesn't work, as in the proxy is never detected.
I think it doesn't run at all, as I added a breakpoint in ProxyDetector.OnRequestEvent and it didn't trigger.
The logs from that event doesn't appear either. websockets-proxy-autodetect.log
My guess is that something in the websockets request is different and that Resend event is never used.
For now, I'm running the proxy detectors manually and setting the proxy if so, which works perfectly fine.
The text was updated successfully, but these errors were encountered: