:
http://www.nabble.com/Wicket-1.3-rc1-Relative-URLs-not-working-properly-tf4933399.html#a14150416
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
this message in context:
http://www.nabble.com/Wicket-1.3-rc1-Relative-URLs-not-working-properly-tf4933399.html#a14150416
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
The /1 is the web app context.
Change it to ../ breaks it on the pages that were working before.
One thing I noticed is that if I deploy this to a server which has mod_proxy
set up to hide the /1 it seems to work fine.
j
On Dec 3, 2007 4:10 AM, Johan Compagner [EMAIL PROTECTED] wrote:
and
Sorry for now explaining this properly. My application is deployed within a
context of /1. The Wicket filter is mapped to /* of the app context.
The first page of the site has url of
http://www.somehost.com/1/welcomewhere welcome is mounted as a
bookmarkable page. There is a link from the
WICKET-1205
On Dec 3, 2007 5:16 PM, Jeremy Levy [EMAIL PROTECTED] wrote:
Sorry for now explaining this properly. My application is deployed within
a context of /1. The Wicket filter is mapped to /* of the app context.
The first page of the site has url of
I just upgraded to Wicket 1.3, it was remarkably smooth. It took about 6
hours overall. Every single thing was explained very well in the migration
guide and the things i was looking forward to in 1.3 are working perfectly.
The only issue I am having is if I have a page this is not mounted as a