What are the risks of removing HTTP "web proxy filter" from ISA 2006
Posted on 2010-09-20
SO I've been fighting for a week or so trying to get ISA setup, and keep getting this error
Error Code 12206: Proxy chain loop
Background: The gateway has detected a proxy chain loop. This condition might indicate a configuration problem on a proxy server.
Date: 9/21/2010 12:26:37 AM [GMT]
have tried like a million(slight exageration) rules, and NIC settings, trying to use the machine as it's own proxy, reversing NIC binding orders on and on.
I can get past this by disableing "web proxy filter" on the HTTP protocal but what is the risk of doing so? it just seems like something I don't want to turn off.
what am I loosing in terms of security and accountability by removing this filter?
the technet article I found the web proxy filter work around, says : The disadvantage of this workaround is that outbound HTTP requests from SecureNAT and Firewall clients will then go directly to the Web server instead of being redirected to the Web Proxy filter. Such requests will not be served from the cache, and HTTP application layer filtering will not be applied.
does this mean I'll not be able to block sites, or monitor/block web content?