Perhaps you should file a bug entry on Pound's website. -----Original Message----- From: Barry Books [mailto:[EMAIL PROTECTED] Sent: Monday, April 11, 2005 10:07 AM To: Tapestry users Subject: Re: Pound SSL Solved
I run OSX and Solaris so I don't have a binary that would work, however after thinking about the problem a bit more I may have a solution that works with the standard binary. My problem was I have a firewall with an IP 64.217.80.79 named home.trsvax.com. Pound runs on a machine with an IP 192.168.1.10 so my pound config is ListenHTTP 192.168.1.10,80 ListenHTTPS 192.168.1.10,443 /usr/local/etc/pound/test.pem RewriteRedirect 1 LogLevel 3 UrlGroup ".*" BackEnd 127.0.0.1,8001,1 EndGroup The problem is when a 302 redirect happens Pound does dns lookup of the host in the Location header. In this case that's home.trsvax.com. It then compares it's IP with IP of the host in Location. If they match it rewrites it. If they don't it just lets it pass thru. So on the machine pound is running I added an entry to /etc/hosts of 192.168.1.10 home.trsvax.com Again I have not done much testing but if this way works I think it's the correct solution. Let me know if that works for you. Barry --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
