Thanks Fredrik. The problem occurs when the proxy is not limited to the domain (I hope the terminology is correct), e.g. http://my.domain.com/xxxxx/myapp
I am using Apache Httpd and Tomcat. As always, talking to someone helps! The following https.cong configuration works: ProxyPass /xxxxx/myapp http://myserver:8080/xxxxx/myapp ProxyPassReverse /xxxxx/myapp http://myserver:8080/xxxxx/myapp ProxyPassReverseCookiePath /xxxxx/myapp / I found that I also needed to change the tomcat server.xml configuration as well: <Context docBase="myapp" path="/xxxxx/myapp" reloadable="true"/> Thanks again! Brad -----Original Message----- From: Fredrik Jonson [mailto:[email protected]] Sent: Friday, 9 March 2012 7:30 AM To: [email protected] Subject: Re: Running click behind an Apache proxy [email protected] wrote: > I have just started using Click - excellent framework. I have an > application up and running but I have run into an issue running the > application behind a proxy. I have used Click in environments where Tomcat runs on localhost and is fronted by apache httpd, proxied through mod_proxy. There is nothing particular to Click that makes it more or less suitable for that kind of configuration than any other web framework. Basically all you need is something like this: ProxyPass /clickapp http://localhost:8080/clickapp ProxyPassReverse /clickapp http://localhost:8080/clickapp Can you post the relevant parts of your site configuration in Apache? I assume Apache Httpd and Tomcat, but maybe that isn't your setup? BTW, I do not recall ever needing to use mod_proxy_html, if you use relative url:s - and I belive click does that by default - you won't have any absolut urls in the html documents that needs rewriting. -- Fredrik Jonson
