Thanks for the reply, Henrik. I'm currently testing this on a customer's server. Here are the relevant squid.conf lines:
http_port 80 httpd_accel_host 64.203.133.200 httpd_accel_port 80 httpd_accel_single_host on httpd_accel_with_proxy on acl all src 0.0.0.0/0.0.0.0 http_access allow all cache_peer 64.203.133.200 parent 80 0 no-query login=dartonw:[EMAIL PROTECTED] I've also tried "sibling" rather than "parent". If I go to http://64.203.133.200/test, that's where the authentication is required. Through the proxy, it would be http://proxy.expr.net/test. With this configuration, I get prompted for username/password through the proxy, and when I enter it I get redirected to the actual IP address. Am I doing something wrong? Regards, Darton -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 5:45 PM To: Darton Williams Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] Passing WWW-Authenticate to server in reverse proxy config On Thu, 11 Mar 2004, Darton Williams wrote: > I have a FreeBSD 4.8 system running the latest Squid 2.5 release. It's set > up as a reverse proxy, but I want it to automatically authenticate to the > one device it's supposed to proxy for. In other words, I have a device that > requires username and password (I'm guessing using simple WWW-Authenticate > headers since it's a firmware web server), and I want to pass that info, > transparently to the user, via Squid. There is two ways a) cache_peer based forwarding, using the login= cache_peer option. b) Use a redirector helper to add the login information to the forwarded URL. Squid understands the URL syntax http://user:[EMAIL PROTECTED]/ and will automatically translate this into Basic HTTP authenticaiton. Regards Henrik
