-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Amos Jeffries
Sent: Sunday, February 12, 2017 10:54 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] internal image call busted?
/squid-internal-static/icons/SN.png
On 11/02
On 11/02/2017 2:05 p.m., Tory M Blue wrote:
>
> Path changed, default is wrong
>
> Where the RPM installed it, the default expects /usr/local/blah
> /usr/share/squid/icons/SN.png
>
> Someone may want to figure out how, why this changed??
>
Maybe. It would help if you mentioned where
On Fri, Feb 10, 2017 at 2:58 PM, Tory M Blue wrote:
> Sorry image didn't come through, i'm talking about this error
>
> ERRORThe requested URL could not be retrieved
> --
>
> *Invalid Request* error was encountered while trying to process the
>
Sorry image didn't come through, i'm talking about this error
ERRORThe requested URL could not be retrieved
--
*Invalid Request* error was encountered while trying to process the request:
GET /squid-internal-static/icons/SN.png HTTP/1.1
Connection: keep-alive
The request just from the browser or curl:
http://cache04.prod.ca.domain.net/squid-internal-static/icons/SN.png
Anyone know what could have changed in 3.5.20 CentOS7 to cause this check
to fail? I use it for internal load balancers to note if the system is able
to handle requests.
Not sure why