What should happen, is that Firefox requests URL Goes via squid, Squid sends on firefoxes request headers Apache backend sends "must authenticate" headers These must be picked u by squid and reversed out to firefox, if this is happening, you will see the firefox basic authentication pop-up. Once firefox sees those authentication headers and you fill in the boxes it will send the a header with a payload of base64 encoded username:password This must be proxied by squid to apache for the resource to be allowed back. Firefox should now cache these credentials and resend them every single request, and so on Where does this fail, are you getting the firefox pop up? Sent from my BlackBerry® wireless device -----Original Message----- From: Kaya Saman <SamanKaya@xxxxxxxxxxxx> Date: Wed, 14 Oct 2009 13:10:11 To: <users@xxxxxxxxxxxxxxxx> Subject: Re: .htaccess files not working from internet? intranetaccessfine Firefox plugin is giving me quite an interesting readout and I think I've located the issue which is what Matt Farey has been saying all along about the Squid forwarding of HTTP Auth Basic Headers: I get WWW-Authenticate: Basic realm="Restricted Files" message which I'm pretty sure is this part of Squid: #auth_param basic realm of which after I get an X-cache: MISS message. Time to go to Squid mailing list I think, would you guys agree??? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|