Timo Stamm wrote:
I have a proxy server:
http://proxy.com/
All requests to the proxy must be forwarded to the app server:
http://app.com/.../wicketapp/
I'm having an issue with a similar type of set-up, but this time in the
actual page markup rather than redirects.
I'm using a 1.2 snapshot, and have discovered Wicket has a habit of
constructing URLs in links, etc. to be absolute (i.e. starts with a '/')
like so:
getContextPath() + '/' + getRelativeURL();
So form actions, link hrefs, etc. look like this:
"/contextPath/wicketServlet?params=foo"
When they should look probably just like this:
"wicketServlet?params=foo"
For my old JSP-based stuff, I just make all the URLs relative, and
everything just works. For top level template includes, which need to
work on all pages no matter the depth, I'd set a response param to tell
the include what depth level I was at, and it'd insert some "../"s
appropriately. Not very pretty, but simple and it works.
Is any reasonable way to make all the links/hrefs/etc. in Wicket always
be relative? (Obviously this would need to insert some "../"s for
mounted pages.)
Or is there some other way to fix this? I can't deploy wicket apps on my
production server 'til I've found out how to fix this. :(
Al
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user