Thanks for the confirmation Amos. On Thu, Sep 1, 2011 at 12:04 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On Thu, 01 Sep 2011 13:59:45 +1200, Amos Jeffries wrote: >> >> On Thu, 1 Sep 2011 08:36:30 +1000, Christian Purnomo wrote: >>> >>> Hi All >>> >>> We have a 3rd party application running on an internal webserver. The >>> server & application is a blackbox to us which we don't have any >>> control on. >>> >>> We would like to be able to 'govern' access to certain path of the >>> website and have been looking if Squid can help us with this. >> >> Certainly can. >> >>> >>> Ideally a simple username/password (ncsa based) is sufficient and we >>> would need to be able to map the authenticated user whether they have >>> access to certain path of the website, i.e. >>> our.internal.ip.address/path/subdirectory1 >> >> The squid ACL documentation is here: >> http://wiki.squid-cache.org/SquidFaq/SquidAcl >> >> You need to read the sections 1 through 11. >> >> Amos > > Oh, and when you setup NCSA, please ensure you avoid DES for the password > storage. The squid helper accepts various forms of MD5 out of the box and it > may save you lots of pain changing it later. > > Amos > >
