[squid-users] Multiple authentication schemes on separate ports

From: Jim Luther <fusionfan@dont-contact.us>
Date: Thu, 15 Sep 2005 09:58:43 -0700

Hi,

I've looked through the FAQs, the Wessels Squid book from O'Reilly,
and the postings on this mailing list and could not find the answers
I need

I've set up a Squid server to test our HTTP network clients against.
Our HTTP implementation supports Basic, Digest Access and NTLM
authentication schemes (and others) and so I'd like to be able to
test against a Squid proxy using each of those authentication schemes.

If a 407 response is received with multiple Proxy-Authenticate
headers, our HTTP stack attempts to automatically choose the "best"
authentication scheme (i.e., use Digest Access if possible, else use
NTLM if possible, else use Basic). So since I want to test against
each of those schemes, I cannot just enable them all on a single
proxy port because Digest Access would always be picked.

I'd like to set up Squid so that it listens on 3 different ports and
challenges with a different authentication scheme on each of those
ports. For example:

foo.apple.com:80 <- challenges with only Basic authentication
foo.apple.com:8000 <- challenges with only Digest Access authentication
foo.apple.com:8080 <- challenges with only NTLM authentication

Is there a way to do this in a single configuration file, or do I
just need to have multiple configuration files and start squid
multiple times using the -f option to pass in the different
configuration files?

If I need to run multiple copies of squid, what other changes (if
any) do I need to make to my configuration files so that the
different squid processes don't run into each other?

Thanks,

Jim Luther
Apple Computer
Received on Thu Sep 15 2005 - 10:58:44 MDT

This archive was generated by hypermail pre-2.1.9 : Sat Oct 01 2005 - 12:00:03 MDT