03-18-2004 01:42 AM
Lately, I have observed that more and more commercial ISP proxy servers have turned off X-forwarded as well as other fields. This is a common l33t tactic to hide identity (see: http://www.samair.ru/proxy/faq.htm) and to create anonymous proxy servers.
Is there some new underlying reason why this is happening? Is there some new Squid or Cisco Cache Engine version that turns off X-forwarded-for by default?
Thanks,
Hank
Solved! Go to Solution.
03-18-2004 02:15 AM
Hank,
x-forward-for is off by default on our content engines and I believe it has always been that way.
The x-forward-for is not a RFC header but a vendor specific header which has been adopted by a number of vendors including us.
In a true transparent caching environment you would not want this header added as we could not be fully transparent then.
HTH
Phil
03-18-2004 02:15 AM
Hank,
x-forward-for is off by default on our content engines and I believe it has always been that way.
The x-forward-for is not a RFC header but a vendor specific header which has been adopted by a number of vendors including us.
In a true transparent caching environment you would not want this header added as we could not be fully transparent then.
HTH
Phil
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide