So it looks as if when I don't secure the pages, then tapestry is building relative page links which seems to work perfectly; however when I generate emails with absolute links in them, it seems to generate a link with http:// rather than the secure schema, but with the correct server name from the proxy, however without absolute I get a relative url. If I set it to secure, then I get an absolute secure link with the local server name rather than the proxy server name. Any thoughts on how to handle this without having to manually set the server name?
On Wed, Nov 5, 2014 at 10:13 AM, George Christman <gchrist...@cardaddy.com> wrote: > Hi everyone, my company wants to secure our entire site and handle https > decryption at the proxy and pass the request along to the app server over > port 80. How can I generate the page links as https without having to > secure all the pages? I don't want the app doing redirects to port 443 > because our app server doesn't listen on port 443, only 80. I thought about > overriding baseurl which I could probably do if I just had two server > environments using the production mode boolean, but unfortunately we have 3 > and I don't know how to pass those environments into baseurl. I also know I > could probably secure the links, however I'm looking for an application > wide solution to this situation. Any thoughts? > -- George Christman CEO www.CarDaddy.com P.O. Box 735 Johnstown, New York
