Hi Alex/Team
The end user are receiving an error in the browser stating : "The site can't be reached"and " <URL> took long time to respond ".
So can you assist me to include the custom log format which will provide further details.
So can you assist me to include the custom log format which will provide further details.
[Thu Mar 11 11:02:15 2021].001 119629 10.197.10.140 TAG_NONE/503 0 CONNECT <URL>.amazoncognito.com:443 - HIER_NONE/- -
Regards
Arjun K.
On Wednesday, 10 March, 2021, 07:50:00 pm IST, Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 3/10/21 8:15 AM, Arjun K wrote:
> Can you please let us know what this error means - TAG_NONE/503 in the
> access logs.
Most likely, Squid generated an error response and sent that to the
client. The response was probably generated before Squid made the cache
hit/miss decision.
In modern Squids, adding %err_code/%err_detail to your custom logformat
definition may help detail the error further in some cases. In all
Squids, looking at the Squid error response itself may help detail the
error further.
HTH,
Alex.
> Some times, I get the above error for all the URLs and no one is able to
> reach the internet and now I am facing the issue only for specific URLs.
>
> The concern is that the issue gets automatically solved without making
> any changes to any configuration and it comes back again and again and
> it gets resolved.
>
>
> The below is the configuration in the proxy server.
>
> ###IP Ranges
>
> acl localnet src "/etc/squid/linux_server.txt"
> acl localnet src "/etc/squid/server_allowed.txt"
>
>
> ### URL - Allow / Deny
>
> acl allowedurl dstdomain "/etc/squid/allowed_url.txt"
> acl denylist dstdomain "/etc/squid/denylist.txt"
>
> acl Safe_ports port 80 # http
> acl Safe_ports port 443 # https
> acl CONNECT method CONNECT
>
> http_access deny denylist
> http_access deny !Safe_ports
> http_access allow allowedurl
>
> http_access allow localhost manager
> http_access deny manager
>
> http_access allow localnet
> http_access allow localhost
> http_access deny all
>
> http_port 8080
>
> cache_dir ufs /var/spool/squid 10000 16 256
> coredump_dir /var/spool/squid
>
> refresh_pattern -i
> windowsupdate.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320
> 80% 43200 reload-into-ims
> refresh_pattern -i
> microsoft.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320 80%
> 43200 reload-into-ims
> refresh_pattern -i
> windows.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320 80%
> 43200 reload-into-ims
> refresh_pattern ^ftp: 1440 20% 10080
> refresh_pattern ^gopher: 1440 0% 1440
> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
> refresh_pattern . 0 20% 4320
>
>
> Could you please let me know what causes these issues and how to give a
> permanent fix.
>
>
> Regards
> Arjun K.
>
> _______________________________________________
> squid-users mailing list
> squid-users@xxxxxxxxxxxxxxxxxxxxx
> http://lists.squid-cache.org/listinfo/squid-users
>
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
> Can you please let us know what this error means - TAG_NONE/503 in the
> access logs.
Most likely, Squid generated an error response and sent that to the
client. The response was probably generated before Squid made the cache
hit/miss decision.
In modern Squids, adding %err_code/%err_detail to your custom logformat
definition may help detail the error further in some cases. In all
Squids, looking at the Squid error response itself may help detail the
error further.
HTH,
Alex.
> Some times, I get the above error for all the URLs and no one is able to
> reach the internet and now I am facing the issue only for specific URLs.
>
> The concern is that the issue gets automatically solved without making
> any changes to any configuration and it comes back again and again and
> it gets resolved.
>
>
> The below is the configuration in the proxy server.
>
> ###IP Ranges
>
> acl localnet src "/etc/squid/linux_server.txt"
> acl localnet src "/etc/squid/server_allowed.txt"
>
>
> ### URL - Allow / Deny
>
> acl allowedurl dstdomain "/etc/squid/allowed_url.txt"
> acl denylist dstdomain "/etc/squid/denylist.txt"
>
> acl Safe_ports port 80 # http
> acl Safe_ports port 443 # https
> acl CONNECT method CONNECT
>
> http_access deny denylist
> http_access deny !Safe_ports
> http_access allow allowedurl
>
> http_access allow localhost manager
> http_access deny manager
>
> http_access allow localnet
> http_access allow localhost
> http_access deny all
>
> http_port 8080
>
> cache_dir ufs /var/spool/squid 10000 16 256
> coredump_dir /var/spool/squid
>
> refresh_pattern -i
> windowsupdate.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320
> 80% 43200 reload-into-ims
> refresh_pattern -i
> microsoft.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320 80%
> 43200 reload-into-ims
> refresh_pattern -i
> windows.com/.*\.(cab|exe|ms[i|u|f]|[ap]sf|wm[v|a]|dat|zip) 4320 80%
> 43200 reload-into-ims
> refresh_pattern ^ftp: 1440 20% 10080
> refresh_pattern ^gopher: 1440 0% 1440
> refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
> refresh_pattern . 0 20% 4320
>
>
> Could you please let me know what causes these issues and how to give a
> permanent fix.
>
>
> Regards
> Arjun K.
>
> _______________________________________________
> squid-users mailing list
> squid-users@xxxxxxxxxxxxxxxxxxxxx
> http://lists.squid-cache.org/listinfo/squid-users
>
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
