Re: [squid-users] Bypassing 403 and 404 status to ICAP using icap_access

On Thu, 2008-04-03 at 12:00 +0530, selvi nandu wrote:

> Thanks for the reply. I had submitted a bug report. I am just placing
> few lines from the debug log here for your reference.
>
> 2008/04/03 14:24:58.788| ACLChecklist::preCheck: 0x60000000004dfdc8
> checking 'icap_access class_1 deny HS'
> 2008/04/03 14:24:58.788| ACLList::matches: checking HS
> 2008/04/03 14:24:58.788| ACL::checklistMatches WARNING: 'HS' ACL is
> used but there is no HTTP reply -- not matching.
> 2008/04/03 14:24:58.788| ACLList::matches: result is false
>
> Please let me know if you have some input on this.

A possible fix has been added to your bug report. Please test and
followup there: http://www.squid-cache.org/bugs/show_bug.cgi?id=2294

Thank you,

Alex.

> On 3/19/08, Alex Rousskov <rousskov@measurement-factory.com> wrote:
> > On Tue, 2008-03-18 at 11:42 +0530, selvi nandu wrote:
> >
> > > Here, i don't want the 403 and 404 status to be sent to the ICAP Server.
> > >
> > > I had tried icap_access with http_status but that didn't work for me.
> > >
> > > ICAP configurations used:
> > >
> > > acl HS http_status 404
> > >
> > > icap_enable on
> > > icap_preview_enable off
> > > icap_persistent_connections off
> > > icap_send_client_ip on
> > > icap_send_client_username on
> > > icap_client_username_header X-Authenticated-User
> > > icap_service vicontent respmod_precache 0 icap://172.16.1.225:1344/respmod
> > > icap_class class_1 vicontent
> > > icap_access class_1 deny HS
> > > icap_access class_1 allow all
> > >
> > > Any thoughts to achieve this?
> >
> > I do not see any problem with your configuration. If you do not receive
> > better responses, please file a bug and attach cache.log with ALL,9
> > debug_options enabled when 404 transaction is being processed.
> >
> > Thank you,
> >
> > Alex.
> >
> >
> >
Received on Thu Apr 03 2008 - 01:30:46 MDT