You're right, Matus. That was the issue.
I replace as you suggested:
acl ads dstdom_regex "/etc/squid/ad_block.txt"
by
acl ads dstdomain "/etc/squid/ad_block.txt"
and now it works.
Thank you very much, Matus !
Have a nice day.
Nicolas.
Le 03/12/2022 à 15:02, Matus UHLAR - fantomas a écrit :
O
On 03.12.22 13:52, Nicolas wrote:
I installed squid on one of my servers, in order to block ads.
When I do not activate ads blocking, it works fine.
However, when I do activate ads blocking, some website are not accessible.
I can browse www.google.com for example, but I can't access www.linuxhin
On 6/01/21 6:21 am, Wolfgang Paul Rauchholz wrote:
I run a home server under Centos 7 and squid 3.5.20. The config is still
work in progress as I started only today. Any tipps&tricks are welcomed
The function is as expected when working from my LAN. But when I tested
today from my cell phone fro
NOTE: please dont use fancy quoting when posting through the Nabble
interface. It erases the critical information about your problem from
any other copy of the list:
On 3/12/2016 9:30 a.m., domshyra wrote:
> So I have changed the file to a sample conf file. Here is what it looks like
> now
>
>
>
I tried that but still 403 :/.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-on-raspberrypi-tp4680711p4680723.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users ma
On Friday 02 December 2016 at 21:30:57, domshyra wrote:
> So I have changed the file to a sample conf file. Here is what it looks
> like now
http_access allow all
Looks to me to be your biggest problem.
Standard security practice is "allow what you specifically know you want to
allow,
So I have changed the file to a sample conf file. Here is what it looks like
now
authenticated_ips is a list of ip addresses that are going to be outgoing
ips and 192.168.1.25 isn't part of it. I have received a new 403 error which
is this below
192.168.1.25 is my macbook which is SSH'd into
On 2/12/2016 4:36 a.m., domshyra wrote:
> Hello. I have looked for countless hours to solve this problem.
> I have tried reordering the config file so that
> are all in different orders
>
> I've messed with http_access deny !Safe_ports
>
> None of the regular trouble shooting issues helped.
Bump for the mailing list...
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-on-raspberrypi-tp4680706p4680710.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mail
On 15/10/2015 8:42 p.m., Filip Maroul wrote:
> Hello I am try to configure squid3 on debian 8 x64 version of squid is 3.4.8
> Here is the conf file:
How certain are you that is the config file being used?
The access.log says things are explicitly being denied, which that
config says are allowed.
Thank You.
Now I understand.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-DENIED-403-tp4668210p4668231.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mailing list
squid-u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 9:45 p.m., navari.lorenzo wrote:
> hello boys, excuse my bad english
>
> there is something i don't understand. If i write an URL into a
> browser which use Squid (for example www.xxx.com) (denied whith an
> acl)
>
> I expect that Squid
hello boys,
excuse my bad english
there is something i don't understand.
If i write an URL into a browser which use Squid (for example www.xxx.com)
(denied whith an acl)
I expect that Squid answer saying: you cannot access this url because it is
a denied url.
This should happen without squid goe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/11/2014 10:39 p.m., navari.lore...@gmail.com wrote:
> Good day today. I' m configuring a Squid Web Proxy Cache and I
> apply the deny policy to some sites l this is the problem:
>
> when people accesses sites with GET they have the right html er
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The project 100% needs a wiki article with the relevant information
about the issue.(the page is wonderful!!!)
I can write the page but it will take time to finish.
- - Adding into the todo list.
I am unsure but almost sure a bugzilla report about it
thank for replay
SO = CentOS 7
squid-3.4.6-1.el7.centos.x86_64
=
[root@lv-034-005 squid]# cat squid.conf
#
# Recommended minimum configuration:
#
#Default: debug_options ALL,1
#more: debug_options ALL,1 33,2 28,9
debug_options ALL,1 28,3
thank now i read
Il 05/11/2014 10:53, Rafael Akchurin [via Squid Web Proxy Cache] ha scritto:
> Hello Navari,
>
> Just my two cents -
> http://docs.diladele.com/faq/squid.html#why-i-see-cannot-connect-to-site-using-https-browser-message-instead-of-usual-site-is-blocked
>
> Raf
>
> -Original
Hello Navari,
Just my two cents -
http://docs.diladele.com/faq/squid.html#why-i-see-cannot-connect-to-site-using-https-browser-message-instead-of-usual-site-is-blocked
Raf
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of navari.lore..
On Wednesday 05 November 2014 at 10:39:19 (EU time), navari.lore...@gmail.com
wrote:
> I'm configuring a Squid Web Proxy Cache and I apply the deny policy to some
> sites. This is the problem:
>
> when people access sites with GET they have the right html error page
> ERR_ACCES_DENIED
> (LOG =
Entry created in bugzilla:
http://bugs.squid-cache.org/show_bug.cgi?id=4122
On Mon, Oct 20, 2014 at 7:25 AM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 20/10/2014 6:18 p.m., Tom Tom wrote:
>> Hi Amos
>>
>> Do you have new findings? Should I open a bug for bett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/10/2014 6:18 p.m., Tom Tom wrote:
> Hi Amos
>
> Do you have new findings? Should I open a bug for better tracking?
>
I got nothing new sorry. Yes a bug tracker would be useful to keep
track of it.
Amos
> Kind regards, Tom
>
> On Mon, Oct 13
Hi Amos
Do you have new findings? Should I open a bug for better tracking?
Kind regards,
Tom
On Mon, Oct 13, 2014 at 8:16 AM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 13/10/2014 6:26 p.m., Tom Tom wrote:
>> Hi
>>
>> Does anyone have some ideas/hints concerni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/10/2014 6:26 p.m., Tom Tom wrote:
> Hi
>
> Does anyone have some ideas/hints concerning this problem?
I am looking into it and fairly sure its a bug in how the ACL result
is returning 1 == ALLOWED. But that was done to solve another bug in
auth
Hi
Does anyone have some ideas/hints concerning this problem?
Many thanks.
Tom
On Wed, Oct 8, 2014 at 8:16 PM, Tom Tom wrote:
> I still get a TCP_DENIED/403 while accessing a bumped https-site after
> putting a "-" or even "^root$" in /etc/squid/DENY_USERS_LOCAL. The
> cache.log with "debug_opt
I still get a TCP_DENIED/403 while accessing a bumped https-site after
putting a "-" or even "^root$" in /etc/squid/DENY_USERS_LOCAL. The
cache.log with "debug_options 29,3 28,9" activated looks like this:
014/10/08 20:03:00.539 kid2| Acl.cc(157) matches: checking DENY_USERS_LOCAL
2014/10/08 20:03
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 3:21 a.m., Amos Jeffries wrote:
> On 9/10/2014 2:09 a.m., Tom Tom wrote:
>> I think, this behaviour was introduced with squid 3.4.4.1
>> (http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
>
>> I don't exactly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/10/2014 2:09 a.m., Tom Tom wrote:
> I think, this behaviour was introduced with squid 3.4.4.1
> (http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
>
> I don't exactly understand this behaviour. Any hints for this?
Ah
I think, this behaviour was introduced with squid 3.4.4.1
(http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13113.patch).
I don't exactly understand this behaviour.
Any hints for this?
Thanks a lot.
Kind regards,
Tom
On Mon, Oct 6, 2014 at 11:59 AM, Tom Tom wrote:
> Hi
>
> After
28 matches
Mail list logo
