I found the problem. It was a IP list loaded in Bypass Proxy for These
Destination IPs (I'm using Squid under pfsense 2.3.2-RELEASE-p1) trying to
solve problems with Windows Updates. Delete this list and Voila!. Now
infobae.com is blocked.
Windows Update works out now with steps by Yuri Voinov
(htt
On 26/11/2016 1:34 a.m., chcs wrote:
> I did it all changes, but again, doesnt works out. Please anybody, can test
> this domain (www.infobae.com) for me?.
Somebody else testing a third-pary site is not the answer to something
on your network being broken.
This is what redbot.org says about the
http://img02.imgland.net/IqkhVlQ.png
So?
Add this in squid.conf:
acl ib dstdomain .infobae.com
http_access deny ib
Viola:
http://img02.imgland.net/B4ZhnZm.png
25.11.2016 18:34, chcs пишет:
I did it all changes, but again, doesnt works out. Please anybody, can test
this domain (www.infobae.
I did it all changes, but again, doesnt works out. Please anybody, can test
this domain (www.infobae.com) for me?.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/How-to-block-www-infobae-com-tp4680601p4680654.html
Sent from the Squid - Users mailing list arc
You can simplify this quite a bit which might make things clearer.
Though please ensure that you are using a current 3.5.19 or later since
you are using SSL-Bump feature. Then run "squid -k parse" and erase the
obsolete options from your config file.
On 23/11/2016 12:40 a.m., chcs wrote:
> My s
My squid (3.5.21) conf file:
http_port 192.168.10.1:3128 ssl-bump generate-host-certificates=on
dynamic_cert_mem_cache_size=10MB cert=/usr/local/etc/squid/serverkey.pem
capath=/usr/local/share/certs/
cipher=EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA38
On 22/11/2016 11:09 p.m., chcs wrote:
> This site (www.infobae.com) it seems to be http. My squid configuration is
> transparent and SSL interceptation. Simply I cant doesnt block anyway.
>
You are going to have to show what your config is for any useful help.
Amos
_
On 22.11.16 02:09, chcs wrote:
This site (www.infobae.com) it seems to be http. My squid configuration is
transparent and SSL interceptation. Simply I cant doesnt block anyway.
how are you trying to block?
do you see in logs that the reuests are aceually pass through squid?
--
Matus UHLAR - fa
This site (www.infobae.com) it seems to be http. My squid configuration is
transparent and SSL interceptation. Simply I cant doesnt block anyway.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/How-to-block-www-infobae-com-tp4680601p4680609.html
Sent from the
[mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of chcs
Sent: Tuesday, November 22, 2016 02:39
To: squid-users@lists.squid-cache.org
Subject: [squid-users] How to block www.infobae.com
How to block www.infobae.com, this site is hosted in Amazon AWS.
Can you tell me what's ACL dire
I did it early, but doesnt works out. Please, can you test this domain for
me?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/How-to-block-www-infobae-com-tp4680601p4680604.html
Sent from the Squid - Users mailing list archive at Nabble.com.
/add the domains you want to block to a file listofblockedwebsites.acl/
/prepend each domain with a dot so that all subdomains are also blocked./
/.infobae.com/
/add these two lines to your squid.conf //
//acl infobae dstdomain -i "/etc/squid3/listofblockedwebsites.acl"/
/http_access deny inf
How to block www.infobae.com, this site is hosted in Amazon AWS.
Can you tell me what's ACL directive?.
Thanks.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/How-to-block-www-infobae-com-tp4680601.html
Sent from the Squid - Users mailing list archive at Nab
13 matches
Mail list logo
