Hacks are what I am looking for... I will give this a try. I also thought if I install a servlet filter that changes the request on the SSL proxied port (8080) to look like https instead of http.. i.e.
HttpServletRequest.getRequestURL() = "https://"; HttpServletRequest.isSecure() = "true" etc, etc... Paul Cantrell wrote: > You might be able to fix it by doing something like this: > > public class MyDecoder extends > org.apache.tapestry.workbench.RequestDecoder { > public DecodedRequest decodeRequest(HttpServletRequest > request) { > DecodedRequest result = super.decodeRequiest(request); > result.setScheme("https"); > return result; > } > } > > In your tapestry.application: > > <meta key="org.apache.tapestry.request-decoder" > value="my.custom.MyDecoder" /> > > It's a hack, but might work. > > Cheers, > > Paul > > > On Jan 3, 2006, at 11:16 AM, Glen wrote: > > >>For reasons out of my control I have a webapp that runs on port >>8081 and >>has an SSL proxy/accelerator in front of it on port 443. >> >>What I am seeing is that when the request comes in from the proxy >>if the >>url in the browser is https://myserver.com:443... The url for my >>external link and redirects is http://myserver.com:443... >> >>Is there anyway to fix this? I have heard mentione before a url >>listener/rewriter. Would this work? Would it work for external >>link, >>direct link, and redirects? > > > _________________________________________________________________ > Piano music podcast: http://inthehands.com > Other interesting stuff: http://innig.net > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
