<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Ok sorry for this mistake !<div>With only one url_regex ACL, <span style="font-size: 12pt;">i put one domain per line in a file</span><span style="font-size: 12pt;">, will it work ?</span></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;">Thanks !</span></div><div><br><div>> To: squid-users@lists.squid-cache.org<br>> From: eliezer@ngtech.co.il<br>> Date: Wed, 25 Nov 2015 15:30:28 +0200<br>> Subject: Re: [squid-users] squidguard and windows update<br>> <br>> I am biased but both squid and squidguard requires some action when you <br>> need to update the acls.<br>> If you need a small amount of rules it is fine to use squid otherwise <br>> you better try external tools for filtering.<br>> <br>> Eliezer<br>> <br>> On 25/11/2015 13:51, Amos Jeffries wrote:<br>> > Wait up.<br>> ><br>> > Magic has been fooled by the marketing words into thinking a "deny page"<br>> > from SquidGuard actually denies something. It does not.<br>> ><br>> > All SG does. All it ever can do. Is tell Squid where to fetch the URL<br>> > from (rewrite), or to tell Squid to tell the client to try somewhere<br>> > else (redirect).<br>> ><br>> > What Magic is thinking of as a "deny" is actually just a statement<br>> > "here, fetch the data from 127.0.0.1". Then the SG (aka. 127.0.0.1) when<br>> > asked responds by dumping out its HTML "error page" text as the reply.<br>> > This unexpected response completely breaks whatever the client needed to<br>> > fetch. If the client is a browser then it happily displays the HTML<br>> > response (as seen in the test described), otherwise it just*breaks*<br>> > whatever application was running.<br>> ><br>> > I expect the real clients are seeing lots of very annoying WindowsUpdate<br>> > 8002something errors, getting pissed off, and then working to bypass the<br>> > "that damn proxy" which is breaking their Windows machines.<br>> ><br>> > What this means for Squid (and sarg) is that the lines above get logged.<br>> > The server SG told Squid to contact*did* respond and the response*was*<br>> > an "HTTP/1.1 200 OK" reply message.<br>> ><br>> ><br>> ><br>> > Magic; I suggest you drop SG and use squid.conf ACLs instead. Everything<br>> > SG can do so can Squid itself.<br>> ><br>> > Amos<br>> <br>> _______________________________________________<br>> squid-users mailing list<br>> squid-users@lists.squid-cache.org<br>> http://lists.squid-cache.org/listinfo/squid-users<br></div></div></div>
</div></body>
</html>