Hi George,
idk but why would you want relative URIs for rev.proxy/loadbalancer
siches? ../../to/page
Looks like it's always absolute dude - as in href="/blah/path/to/page"
The hostname is not written into the URI.
I've just checked my delivered html behind httpd->tomcat and URIs are all
absolute (on 5.4-beta-22).
During this week I changed from a staging subdomain, without context paths
set, to context path set, to test domain and this absolute URI stuff has
worked flawlessly. I haven't tested https though, but on other
non-tapestry sites, https -> 127.0.0.1:8080/ and https -> 127.0.0.1:8180/
I have done limited testing with tapestry.hostname when I was having
tomcat proxy connector config problems (due to forgetting that the
proxyName arg was set there, and my form-post-redirects were landing on
the proxyName address rather than the domain) but i haven't figured out
when I'd need to use that.
From configuration page:
tapestry.force-absolute-uris
Deprecated since 5.2
Icon
Starting in Tapestry 5.2, the optimization to generate relative URIs has
been removed, and all URIs are always absolute. Removed in 5.3.
For Tapestry 5.0 and 5.1 only: when false (the default), Tapestry will
attempt to optimize URIs that it generates, using relative URIs when such
URIs are shorter than absolute URIs. When true, all URIs will be absolute
URIs (including the context path, and the complete path for the request).
On Fri, 31 Oct 2014 04:00:24 +1100, George Christman
<gchrist...@cardaddy.com> wrote:
How do I get Tapestry to use relative urls rather than Absolute? My apps
are hosted behind reverse proxies and load balancers which forward all
http
and https request off as http over 80 to the app servers. Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
