Squid 3.1.20 pkg 2.0.6 header issue?
-
I face some difficulties to access some of the website, and finally figure out it's about the presence of proxy.
With Squid3, the proxy detection was always positive with the Header leakage.
With Squid2, the proxy detection was always negative, and everything works fine.
(You may try with http://whatismyipaddress.com/proxy-check)I have successfully replicated the case with newly install pfsense (2.0.3-RELEASE) on three different VM. May i know if anyone face the same issue?
Just go "google" a while, some suggest that squid3 requires special flag during compile to support the "Disable X-Forward" and 'Disable VIA" features which suppress the header.
-
hmm, i'm running the same version on 2.1beta x86 and it is not detecting my proxy server.
-
hmm, i'm running the same version on 2.1beta x86 and it is not detecting my proxy server.
Thanks, if it's the case, it's possible that the problem is fixed in the 2.1 beta version and remains not fixed for the stable version 2.0.
-
Seems nobody else face the same issue?
-
I have seen the same issue.
Running pfSense 2.1-Release, Squid package 3.1.20 pkg 2.0.6, with Transparent Proxy, Disable X-Forward, and Disable via, Suppress Squid Version all selected. Proxy checker at http://ip.my-proxy.com/ verifies that the HTTP_X_FORWARDED_FOR header is still present, only changed from the IP of the source machine to "unknown".
Is there a fix?
Thanks,
–jg3
-
Ok, I solved this, here's how:
in the Custom Options field at the bottom of the Squid General Settings tab I put the following lines:
# privacy stuff so squid is undetectable via off httpd_suppress_version_string on forwarded_for delete… and saved the config. I believe the real problem is the way the option for "Disable X-Forward" is implemented. From what I can tell only the last line is essential (assuming you tick the "Disable Via" and "Suppress Squid Version" boxes), but these three together are how-to make Squid undetectable.
-
I'll include it on squi3-dev. Thanks for the feedback.
