6, 2017 2:53 PM
Subject: Re: [squid-users] TCP_DENIED/407 accessing webserver on same machine
as squid
Ah, your problem seems to be a misunderstanding of how authentication works.
What Squid receives on messages can have three forms:
1) no credentials at all
2) correct credentials
3) inva
On 27/05/17 07:52, Amos Jeffries wrote:
This is why best practice is to use a "deny" line like so:
http_access deny !auth_users
... which makes it clear what is happening for every non-authenticated
thing, both situation (1) and (2) traffic.
Sorry "both situation (1) and (3) traffic".
Amos
Ah, your problem seems to be a misunderstanding of how authentication works.
What Squid receives on messages can have three forms:
1) no credentials at all
2) correct credentials
3) invalid credentials
Your definition of the auth_users ACL using "REQUIRED" takes care of the
(1) situation. S
all https_port SQUID_PORT cert=/etc/squid/squid.pem cache deny all
netdb_filename none
From: Amos Jeffries
To: squid-users@lists.squid-cache.org
Sent: Friday, May 26, 2017 12:29 PM
Subject: Re: [squid-users] TCP_DENIED/407 accessing webserver on same machine
as squid
On 27/0
On 27/05/17 04:17, j m wrote:
I have a webserver and squid 3.5 running on the same Linux machine. > The webserver is actually part of shellinabox, so it's only for me
to > access. Shellinabox simply presents a terminal and login in a web
> browser. I want it to be accessible only through sq
I have a webserver and squid 3.5 running on the same Linux machine. The
webserver is actually part of shellinabox, so it's only for me to access.
Shellinabox simply presents a terminal and login in a web browser. I want it
to be accessible only through squid for more security.
shellinabox wor
