Hi all, i have huge problem with getting Squid working as a reverse proxy for OWA. I have created a certificate request on my Windows Server 2008, then I have created a certificate and converted it to .pfx. This one I could get into IIS and enable it to my DefaultWebsite in IIS and OWA. So far so good.... Then I have recompiled squid with the --enable-ssl flag on my Debian Server. This is what my ssquid.conf looks like now: .1.199 = Debian Squid .1.249 = Exchange Server visible_hostname my.dyndns.org https_port 192.168.1.199:443 cert=/usr/local/src/sslowa/my.dyndns.org.pem key=/usr/local/src/sslowa/my.dyndns.org.key defaultsite=192.168.1.249 #cache_peer 192.168.1.249 parent 80 0 no-query originserver login=PASS front-end-https=on name=owaServer cache_peer 192.168.1.249 parent 443 0 no-query originserver login=PASS front-end-https=on name=owaServer #cache_peer 192.168.1.249 parent 443 0 no-query originserver login=PASS ssl sslcert=/usr/local/src/sslowa/my.dyndns.org.key name=owaServer acl OWA dstdomain my.dyndns.org cache_peer_access owaServer allow OWA never_direct allow OWA # lock down access to only query the OWA server! http_access allow OWA http_access deny all miss_access allow OWA miss_access deny all I have tried all of the cache-peer things up there, and I have also tried to disable https:// in IIS for OWA. So far no luck there. I do always geht a 403 Access Denied Error, when Im trying to get this site. Of course I have also tried to put defaultsite to defaultsite=192.168.1.249/owa, because OWA is listening on /owa. Please help Obi-Wan Kenobi you are my last hope! Greetings -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
