We have been using several squid servers in accelerator mode for a number of
years mainly for load balancing to send public requests to backend servers.
The requests to the squids typically come via a well known commercial caching
service. The squids don't do any caching, they just forward r
Thanks Amos
The Icap also does url filtering so it's a one stop shop for everything. I have
to stay with V3.5 for the moment but will move up to 4.x later and re-examine
my approach based on the newer features available.
Cache-Control is much cleaner and it actually is named as per what I want
Hello Schroeffu,
Somehow I've manage to miss this last sentence
I have another proxy in production that is working with ACL's like this, but
showing the same error ""TCP_DENIED/407"
That is why i decide to build new one and find the "problem".
Probably will try new one with kerberos.
Thank you ve
Hi Stan,
when you are using NTLM according the latest sentence in
https://wiki.squid-cache.org/ConfigExamples/Authenticate/Ntlm (very bottom):
"Note that when using NTLM authentication, you will see two "TCP_DENIED/407"
entries in access.log for every request. This is due to the challenge-resp
Hello Schroeffu
I fully agree with you, but why some of request are authenticated and some
are not.
Is this a normal behavior.
Thank you for your help.
Stan
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
For my understanding, with (NTLM) authentication every request needs to be
authenticated. Therefore you will see TCP_DENIED/407 anytime before TCP_***/200
because the request needs to be authenticated anytime again.
Anybody else correct me if I am wrong ;-)
Schroeffu
4. Dezember 2019 15:09,
Hello everyone, I'm facing some problem with squid.
Squid proxy is working but in access.log is showing TCP_DENIED/407 for most
of the connections.
If i remove authentication configuration from squid.conf this error is
missing in access.log.
CentOS Linux release 8.0.1905
4.18.0-147.6.el8.x86_64
S
Hi everybody,
I'm using debianedu (stretch) with squid 3.5.
I would like to configure my squid through a parent proxy (172.16.103.254:3128).
I give you my issues at the beginning of this post, and my squid config at the
end.
-> When I start squid on my debian stretch, and check if everything is
finally solved it and its working really nicely
what i did was to monitor the "access.log" using the watch and tail command
to see what websites it was actually going to
#Block MIME types
acl mimetype urlpath_regex -i \.exe$ \.msi$
http_access deny mimetype
#HTTPS whitelist websites
acl whitelis
On 4/12/19 11:29 pm, tomsl wrote:
> I have an odd issue running squid 4.2 as a reverse proxy in front of
Please upgrade. Current Squid-4 release is 4.9 and there are quite a few
very major security issues and bugs resolved since 4.2. Some of which
are related to cache corruption.
>
> Is there a
I have an odd issue running squid 4.2 as a reverse proxy in front of
rackspace cloudfiles. For some reason, something went wrong when the request
was made initially and squid has cached a broken response. The headers
returned by squid are as follows:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Last-Modif
11 matches
Mail list logo
