The URL for the login form does not contain the full URL to the server, so why does Tapestry respond with the IP address?
--Michael On Mon, Sep 19, 2011 at 1:07 AM, Michael Molloy <tapestrya...@gmail.com>wrote: > One other thought. Looking over the http://tapestry.apache.org/https.htmlpage > 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