On 10/30/2017 10:16 AM, Amos Jeffries wrote:
>
> Between them these entries appear to be saying that you have very
> probably configured the Squid machines host name as "sma-server3"
> instead of "proxy1.sma.com".
>
"proxy1.sma.com" is an alias for sma-server3.sma.com.
I have tried using sma-
On 30/10/17 12:01, James Moe wrote:
On 10/29/2017 04:54 AM, Amos Jeffries wrote:
What does access.log show for the manager request?
The above port is IPv6-enabled but the manager_admin ACL only allows an
IPv4.
1509311060.445 15 192.168.69.115 TCP_MISS/403 4464 GET
http://proxy1.sma.com:3
On 10/29/2017 04:54 AM, Amos Jeffries wrote:
>
>> #
>> http_access allow manager_admin manager
>> http_access deny !Safe_ports
>> http_access deny CONNECT !SSL_ports
>> http_access allow localnet
>> http_access deny all
>
> Two things:
>
> 1) 'manager' is a pre-defined ACL. The your redefinition
On 29/10/17 20:02, James Moe wrote:
Hello,
opensuse v42.2
linux v4.4.87-18.29-default x86_64
squid v3.5.21
On occasion I look at the squid statistics; it has been a while since
I last checked them, at least a month. The request was denied as not
having access privileges. I do not s
Hello,
opensuse v42.2
linux v4.4.87-18.29-default x86_64
squid v3.5.21
On occasion I look at the squid statistics; it has been a while since
I last checked them, at least a month. The request was denied as not
having access privileges. I do not see why it is now being denied.
My understa
