Hello Alex,
Thank you for clarifying, that makes a lot more sense when you put it like
that. So the request to go to that internal website is not being authenticated
when browsing to it via hostname. But it *does* authenticate when browsing to
it manually via IP. So one of the ACL's we have in
Hello Amos,
While the comments did say that it was just the 10.46.11.0 range, I don't think
there's any other ACL forcing that. I tried adding the the two internal sites
that are being blocked by their IP, restarted Squid, and tested. Still being
blocked. You are right though, both of those we
On 05.09.24 14:52, YAMAGUCHI NOZOMI (JIT ICC) wrote:
If there were duplicate domains in the list of domains used, restarting the
squid would cause the process to stop.
Below is the error statement.
ERROR: 'a.example.com' is a subdomain of 'example.com
Why do you keep duplicates on config?
you c
I'm sorry. I forgot to attach the configuration file used in the
verification (partially masked).
2024年9月5日(木) 17:58 にば :
>
> Hi Alex
>
> Thanks for the reply !
>
> I took the advice I received, reviewed the verification details, and
> verified again with the two recommended steps.
> The new verif
Hi Alex
Thanks for the reply !
I took the advice I received, reviewed the verification details, and
verified again with the two recommended steps.
The new verification includes the following four patterns:
1. successful communication of a valid request to an allowed site
[command]
curl https://py
