On Friday 17 May 2013 13:36:07 Delton wrote: > Using the dstdomain http://www.facebook.com is blocked and you receive > the error page of Squid, but when accessing https://www.facebook is > displayedthe proxy server connection refused, not the Squid error page. > > Em 17/05/2013 11:57, Amos Jeffries escreveu: > > On 18/05/2013 1:41 a.m., Hussam Al-Tayeb wrote: > >> On Friday 17 May 2013 09:21:55 Jose Junior wrote: > >>> Personnel, the company where I work she, I need to block facebook, I > >>> can but it affects the connection with other sites such as gmail > >>> > >>> thank you very much > >> > >> acl blockedurls dstdom_regex -i "/etc/squid/squid.blockedurls" > >> http_access deny blockedurls > >> > >> add this to /etc/squid/squid.blockedurls > >> > >> (^|\.)facebook\.com$ > >> > >> this blocks http://anything.facebook.com > >> > >> but your users will still be able to access > >> https://anything.facebook.com > > > > Just doing these is *exactly* equivalent to the above: > > acl blockedurls dstdomain .facebook.com > > http_access deny blockedurls > > > > And both ways of writing it will block HTTPS traffic as well as HTTP. > > > > Amos It depends on whether you are routing https traffic thought squid or not. Almost not ISP routes https traffic through proxies.