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
NO_PROXY has a pitfall where users will intuitively want to do NO_PROXY=some-external-site.net, but this also means that localhost will be sent through the proxy, which almost never makes any sense to do.
Desired behavior:
Always consider localhost to be in NO_PROXY unless <-loopback> is included (same contract as Chrome's --proxy-bypass-list
The code for this is done in cypress-io/cypress#4800, but has yet to be released.
We'll update this issue and reference the changelog when it's released.
Current behavior:
NO_PROXY
has a pitfall where users will intuitively want to doNO_PROXY=some-external-site.net
, but this also means thatlocalhost
will be sent through the proxy, which almost never makes any sense to do.Desired behavior:
Always consider
localhost
to be inNO_PROXY
unless<-loopback>
is included (same contract as Chrome's--proxy-bypass-list
NO_PROXY=example.com
=>NO_PROXY=localhost,127.0.0.1,example.com
NO_PROXY=example.com,<-loopback>
=>NO_PROXY=example.com
The text was updated successfully, but these errors were encountered: