Thank you Amos as always.
My current configuration has not changed much, it is as follows:
visible_hostname s-px4.mydomain.local
http_port 3128
error_directory /opt/squid-503/share/errors/es-ar
forwarded_for transparent
shutdown_lifetime 0 seconds
quick_abort_min 0 KB
quick_abort_max 0 KB
quick_ab
On 29/09/20 3:55 am, Service MV wrote:
> In my case I have the domains, for example from webex, which I get from
> their official support page. It seems that I am doing something wrong or
> I am not understanding well.
> I base on this documentation
> https://wiki.squid-cache.org/ConfigExamples/Aut
In my case I have the domains, for example from webex, which I get from
their official support page. It seems that I am doing something wrong or I
am not understanding well.
I base on this documentation
https://wiki.squid-cache.org/ConfigExamples/Authenticate/Bypass
The error I get is 407. I under
I looked this up an it looks like the reason Google does not work with
Kerberos authentication (I think) is that Google makes requests to other
domains:
https://serverfault.com/a/307605(Please look at the second comment of the first
answer.)
The solution would be to create an ACL to allow the
Hello everyone, I am trying to deal unsuccessfully with proxy
authentication bypass.
Even looking at the documentation I can't get it right. The point is that
certain programs such as being a cisco webex client or the google earth pro
client do not know how to speak well with SQUID's kerberos authe
