Turns out creating a filter that wrapped the request and response to
look like an https request to the proxied port (i.e. the port the web
browser was connecting to the proxy on as opposed to the port the server
was listening on) provided a general solution that worked in tapestry
and the non-tapestry pages with no application changes needed.  Where
the other solutions required individual changes in each framework.

To provide more details I created

HttpServletRequestWrapper that override
    isSecure()
    getScheme()



HttpServletResponseWrapper that override
    sendRedirect()




I also rewrote the requestUrl to have https instead of http...





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]

Reply via email to