Yes. See http_access and acl types "method" and "dstdomain".
Will still be logged, and the user will be send a error page instead of
the intended result. Which error page the user sees can be controller by
deny_info.
-- Henrik Nordstrom Squid Hacker Steve Snyder wrote: > > Is there any way with Squid, either 2.3STABLE4 or v2.4STABLE1, to block > POSTs to a specific domain? > > Ideally I'd make the requests below just disappear, with the incoming > request (POST) having no effect on the cache nor entries made in the > access.log. My second-best behavior would be to simply prevent these > action from being passed to the destination domain. > > Is this possible? Thank you. > > ----------------------------- > > TCP_MISS/200 213 POST http://updateserver.gator.com/CMD/AutoUpdate - DIRECT/updateserver.gator.com text/html > TCP_MISS/200 193 POST http://bannerserver.gator.com/bannerserver/bannerserver.dll? - DIRECT/bannerserver.gator.com - > TCP_MISS/200 261 POST http://bannerserver.gator.com/bannerserver/bannerserver.dll? - DIRECT/bannerserver.gator.com text/html > TCP_MISS/200 207 POST http://gs.gator.com/Cmd/client_log_event - DIRECT/gs.gator.com text/htmlReceived on Sun May 13 2001 - 14:40:15 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:59:57 MST