[squid-users] squidGuard: redirect to squid-internal URLs no longer working with 3.5?

[Silamael]

On 03/15/2016 12:10 AM, Amos Jeffries wrote:
> On 15/03/2016 2:22 a.m., Silamael wrote:
>>
>> On 03/14/2016 02:16 PM, Kinkie wrote:
>>> Hi,
>>>   .. has it ever? internal:// doesn't seem like a recognized protocol to me.
>> It worked till the update to Squid 3.5.
>>
> 
> It should not have. That was a bug.
> 
> The correct syntax for 'internal:' URI looks like:
> 
>   internal://$visible_hostname:3128/squid-internal-static/...

Sorry, I don't get it. Formerly we had
internal://squid-internal-static/error-access-denied and this resulted
in the ERR_ACCESS_DENIED page being delivered to the client.
Now you say this has been wrong all the time and the correct path would
be internal://$visible_hostname:3128/squid-internal-static/...
So, if i try this, i get a 404 response and the ERR_INVALID_REQ page.
With debugging I can see that there is a request like
GET ://127.0.0.1:3128/squid-internal-static/error-access-denied
This is indeed an invalid request...
If I use http:// instead of internal:// the whole request is forwarded
to the upstream cache peer and again replied with ERR_INVALID_REQ...
With
internal://$visible_hostname:3128/squid-internal-static/error-access-denied
the response is a 400 Bad Request with ERR_UNSUP_REQ.
According to debugging here again the internal schema is not passed
along when building the GET request.

BTW, the old URL I used worked for years!

-- Matthias