You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firefox uses the http proxy environment variables for websockets connections. Their UI also has settings http/https/socks only, notably it does not have a separate option to configure websockets requests.
It's well known that Websockets is an HTTP based protocol, so I expected it to use HTTP configuration.
WebSockets isn't any more an HTTP protocol than GRPC, which uses the same
upgrade mechanism to switch from HTTP to use its own completely different
protocol. It will be bagder's call whether or not it makes sense to use
http_proxy for WebSockets as well. If multiple other programs do it, then it's
an easier sell.
If multiple other programs do it, then it's an easier sell.
Agreed. It makes sense to follow established behaviors.
I find it a little strange to support http_proxy and https_proxy for ws and wss simply because it breaks the previously established pattern. It has always been [url scheme]_proxy to check for the proxy, but this asks for something else.