Re: [squid-users] TCP_DENIED_RELY 302 for error_map

Hi Amos,
   Thanks for your suggestion.

Configuration
-------------------

Squid version: 3.1.20

acl denied_status_404 http_status 404
deny_info 404:http://example.com/ denied_status_404
http_reply_access deny denied_status_404

1) If i try the above configuration browser is not redirectiong to
example.com webpage. Instead I am getting page cannot be displayed.

2) Also access.log is still reporting 302 status code instead of 404.

    "263 172.19.131.179 TCP_DENIED_REPLY/302 365 GET
http://www.google.com/index1.html..... "

Am I missing anything?

On Thu, Jul 3, 2014 at 7:48 AM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 2014-07-03 06:10, SaRaVanAn wrote:
>>
>> Hi All,
>> Recently I have migrated from squid 2.7 to squid 3.2, which forces
>> me to replace an existing error_map configuration with below access
>> list to achieve the same
>>
>> acl denied_status_404 http_status 404
>> deny_info ERR_404.html denied_status_404
>> http_reply_access deny denied_status_404
>>
>> but if i use this configuration access.log is reporting the 404 http
>> status as TCP_DENIED_REPLY 302. I just want to capture the HTTP 404
>> error codes for statistics. Because i could able to capture
>> the HTTP 404 error codes with old error_map configuration
>>
>> Is there any configuration in squid to achieve this?
>
>
> Please read the section in http://www.squid-cache.org/Doc/config/deny_info/
> on 4xx and 5xx error codes to see what is going wrong.
>
> The 302 is generated when you provide a full URL to deny_info. To replace an
> error status reply retain the same status code in the deny_info format:
> deny_info 404:ERR_404.html denied_status_404
>
> Amos
Received on Mon Jul 07 2014 - 20:38:11 MDT