Re: [squid-users] Squid cannot redirect to an HTTP 302

Hi Amos,
    That did the thing!!
Also thanks for the note.

On 6/16/12, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 16/06/2012 12:54 a.m., Chaitanya Shastri wrote:
>> Thanks for a quick reply. We only have a few content types allowed for
>> the intranet clients. The page which I am trying to access has the
>> content type application/xml which I
>> have
>> already put in the allowed content types.
>> How do I permit 302 status through squid?
>
> With an HTTP status ACL.
>
> Place this at the top of your http_reply_access lines:
>
> acl okStatus http_status 302
> http_reply_access allow okStatus
>
>
> NOTE:
> HTTP contains a lot of things which do not necessarily have a type
> associated. You probaby want to increase that to include all other forms
> of redirect (300-399) and HTTP control status messages (100-199). Maybe
> also error responses (400-599), although these are expected to have
> bodies it is a *very good* idea to let them through unaltered.
> Which leaves you with the 200-299 range which are expected to have
> various body content types.
>
> acl limitedReplies http_status 200-299
> http_reply_access allow !limitedReplies
>
> Amos
>
>
Received on Sat Jun 16 2012 - 11:09:00 MDT