tis 2007-05-01 klockan 22:49 +0100 skrev Gareth Edmondson:
> Now this threw up an error along the lines of having two cache_peer
> names the same. So we edited the hosts file in DNS setting a name to
> resolve to the same IP address. The line now reads:
>
> cache_peer sslproxy 443 parent 7 <and then all the other stuff>
There is a name= option to cache_peer to solve this without having to
fake host names..
> We thought this would work - but it didn't, so we edited the
> cache_peer_access line to say 'cache_peer_access sslproxy allow CONNECT'.
You also need to deny CONNECT from the other..
> Everything seems to be working. However when we try and connect to the
> 443 website it challenges us again for the AD username and password.
> Upon entering this the browser challenges us again and again and again -
> simply not letting us through.
What does your access.log say?
Regards
Henrik
This archive was generated by hypermail pre-2.1.9 : Fri Jun 01 2007 - 12:00:04 MDT