On 12/07/17 07:00, avi_h wrote:
Hi Alex,
Thanks for this.
I can narrow it down, as you mentioned, I want to configure Squid to make
some server(s) think that the
request is coming directly from a user agent (e.g., browser).
However, I don't know what those servers use to detect proxies, any idea on
how I can figure it out?
I start with a copy of the HTTP traffic. Both the messages coming from
the client and the ones going to the serve. For both the proxied and
non-proxy traffic.
I then run a set of scripts I've built up over the years to see how the
server responds to various of the header changes the proxy does, and
some possible alternatives. That usually leads to identifying what the
server will accept and what makes it crash or produce errors. Usually
server crashing with uncommon normal inputs are the real problem, not
the proxy "breaking" traffic.
If you will list the websites you are having trouble with and what
behaviour you want to see happen vs what they currently do that would be
a good start.
Ideally, I would like to find a solution that would fit all (or the most
popular) detection mechanisms, if that's possible.
The solution is usually to accept that there is not actually a problem.
The average web object goes through something like 4-6 intermediaries
(ie. proxy) before it arrives at an end users Browser. You have a proxy,
everybody else does too. Nothing to gain by hiding.
In fact, hiding the proxy means literally revealing its users and some
of your internal network structure to any web server they visit. Loosing
privacy and a bit of security too. It is a lose-lose situation.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
