-
Notifications
You must be signed in to change notification settings - Fork 40
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
does not recognize 'no proxy for' setting (in Firefox) properly #63
Comments
Do you mean "No proxy for" in That setting is only applicable when setting a Remote PAC. Try setting it in Global Exclude. |
The network on the LAN is 192.168.0.0/24 and version 8.2 doesn't proxy 192.168.178.* any more. Regex rule is ^https?://192.168.178(.\d+) (not working) but e.g. ^https?://10.0.0(.\d+) is working. Even if I am selecting the proxy manually (for all traffic) it's showing in the log 192.168.178.1 is not sent to the proxy. I downgraded to version 7.5.1 and everything is fine again. |
192.168.0.0/16 is set as global exclude in FoxyProxy in Firefox since it is local network. Do you want to go to 192.168.0.0/16 via a proxy? |
192.168.0.0/24 is the local network. I want to go to 192.168.178.0/24 via a proxy. There is no such thing as a Class B network. |
Previously: #50 |
It seems to me as if this is a different issue. Localhost 127.0.0.1/8 is a different issue from 192.168.0.0/24 not being 192.168.0.0/16. |
FoxyProxy 8 is hardcoded to bypass proxy for localhost and local networks. The issue of local network proxy bypass is discussed in #50. |
The internet is classless. If I'd like to route 192.168.0.0/30 (on the internal network) that's ok with every RFC I know. The same goes for proxying. There is absolutely no reason to exclude rfc6761 (former rfc1918) IP space. |
I am discussing the issue with the founder of FoxyProxy and some or all of localhost checks will be removed in v8.4 |
It is done in v8.4 |
Browser: Firefox 120.0.1
OS: macOS 14.2
If e.g. 192.168.0.0/24 is set in the Firefox 'no proxy for' setting. FoxyProxy 8.2 is not proxying for 192.168.*.*.
The text was updated successfully, but these errors were encountered: