Re: [SQU] Authorization

That is another question, but this too is a possibility.

To enable "proxy" authentication in Squid when running as an
accelerator, add

#define AUTH_ON_ACCELERATION 1

to the top of src/acl.c

and then rebuild Squid (make install).

In normal operation the real server does all authentication, and Squid
MAY be allowed to cache objects as public (not requiring authentication)
even if the client request carried authorization information by the use
of the proper reply headers.

--
Henrik Nordstrom
Squid hacker
Zathmyre wrote:
> 
> So can I have my httpd-accelerator authenticate users? If so, can someone
> please either walk me through real quick or point me in the right direction?
> 
> ----- Original Message -----
> From: "Henrik Nordstrom" <hno@hem.passagen.se>
> To: "Zathmyre" <zathmyre@avalon.net>
> Cc: <squid-users@ircache.net>
> Sent: Wednesday, February 21, 2001 12:27 AM
> Subject: Re: [SQU]
> 
> > Per RFC2616 section 14.8. Not cached unless the origin server explicitly
> > tells the cache that this object may be cacached.
> >
> > Not all of the cache-control directives in that section are supported
> > yet.
> >
> > --
> > Henrik Nordstrom
> > Squid hacker
> >
> > Zathmyre wrote:
> > >
> > > I'm running squid as an httpd-accelerator for a server that uses
> > > authentication. How does squid handle these types of requests? Does it
> > > cache them? And if so, does it still authenticate when the next client
> > > hits it in the cache? Thanks -zathmyre
> >
> >
> 
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html