Jay, > I believe the HTTP server instance does not allow both protection of both > user ids and validation lists in the same instance. In this case I am attempting to use %%CLIENT%% for the areas which must be protected and QUSER or some fixed user for areas that do not require authentication. As you mentioned it's real easy to protect the world, "Protect http:*", but there is no 'except...'. So what I think I need to do is a second "Protect" that uses a different protection group which I uses a fixed profile. Doesn't seem to work though. <snip> > In one tact it doesn't make sense. You would like trusted users to get to > very secure areas and less than trusted, only access to other areas. <snip> Since this is a Caching Proxy to the Internet, they want users who have userid's and passwords to be able to use the entire internet, and those without to only see selected sites of the administration's choosing. We would prefer not to have to use two Web Server instances because that means the PCs need be set up with different Proxy settings. It likely also means separate Caches which partially defeats the purpose. - Larry -- Larry Bolhuis Arbor Solutions, Inc. (616) 451-2500 (616) 451-2571 -fax email@example.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.