[squid-users] Accelerator and authentication

Hi, newbie on the list - I have searched the archives, and not found a
relevant thread, so I'd like to get some ideas.

We run a fairly complex collection of websites - 70+ - on a big-ticket
content management system. The sites are served from 4 Solaris/Iplanet
servers, and use URL rewriting to allow all the sites to share a common
directory structure - http://foo.com/bar/q1234.html and
http://bar.com/bar/q3456.html live in the same directory, the filename is
the distinguishing element.

As the content management system is not performing particularly well, we are
using 4 squid http accelerators (one per "main" web server") to cache
content in acceleration mode - and it works extremely well !

The next thing we want to be able to do, however, is introduce authorisation
for big parts of the sites - only registered users can get access to
http://bar.com/bar/q3456.html , but everyone can get access to
http://foo.com/bar/q1234.html.

The obvious way to do this is to switch off caching for the pages that
require authorisation; this will cause significant performance problems and
is not too popular.

Is there any way in which Squid can do some basic authentication (almost
certainly cookie-based) prior to serving a page - either from the cache or
direct ?

Ta !

Nev
This e-mail and any attachments are sent in confidence. If you received it
in error (a) please tell us by return e-mail and then delete it and (b) you
must not use, forward or otherwise disclose its contents in any way. Premium
TV have taken every reasonable precaution to ensure that any attachment to
this e-mail has been swept for viruses. However, it cannot accept liability
for any damage sustained as a result of software viruses and would advise
that you carry out your own virus checks before opening any attachment.
Received on Fri Nov 09 2001 - 08:01:06 MST