One other thought. Looking over the http://tapestry.apache.org/https.html page again, I notice that it is saying there is a need for that method if your application has some pages that are secure and others that are not. In my case, all of mine are secure, so I would think I could just use relative URLs, but Tapestry seems to be generating absolute URLs based on the internal server IP rather than the external domain name.
Is that a setting that I can change so that it only generates relative URLs? --Michael --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
