T4 works fine is you just enable HTTPS in your servlet container. However if you are trying to offload HTTPS (which is often a good performance choice) to Apache or something similar you may have issues. I don't use mod_rewrite but I have hit issues using an SSL offloader (which works essentialy like mod_rewrite) are
- The redirect filter needs to have explicitly set the https url otherwise the redirect from / to /app fails - The logic to determine the URL when redirecting, setting the base URL for Shell and various other places does not work. The latter can be solved by providing an alternative implementation of the URL builder service that forces a https URL. See http://www.nabble.com/Tapestry-4%2C-Base-HREF-and-SSL-Offload-hardware-t1407511.html#a3790244for a previous thread on this. Ben On 4/20/06, Mark <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > a while back, before T3 was out, somebody I talked to said that doing > https with Tapestry was a pain because of some special things that had > to be considered. > Unfortunately, that was before I worked with Tapestry, and I don't > remember what exactly the problem was there. > > So I am wondering if there is anything that has to be considered when > developing apps that are running under https. > > Right now, we are running apache httpd to do the https decryption and > are proxying the decrypted requests through to Tomcat by using > mod_rewrite. > Can I do the same thing with T4 apps? I think there might be problems > with the cookie-based session handling due to the URL rewrite?! > > Thanks, > > MARK > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
