Thijs wrote:
I need the full path to the bookmarkable page to get this working
What do I have to change to get this working again?
I need to fix WICKET-609 to make this easy for you. ;-)
The reason this has become difficult in Wicket 1.3 is that we now
generate relative URLs so sitting behind a mod_proxy Just Works(tm).
However, that now means that Wicket doesn't really know or care about
the servlet context path bit of your deployment, or the domain name it's
all sitting on.
This is a good thing, as relying on those when you're behind a mod_proxy
breaks everything.
The only way to make this work until I've fixed WICKET-609 is to use the
urlFor() method and manually add the appropriate domain name and path on
to the front of your URL.
Regards,
Al
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
