THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Where <contextPath> is replaced by the context path you've deployed your wicket application under.
The
| Code Block |
|---|
ProxyPass |
directive causes request URLs to be proxied to the specified host. The
| Code Block |
|---|
ProxyPassReverse |
directive causes 302 redirects from your app server to be rewritten to point to the front-end proxy instead, so they continue to work properly.
...
Many people like to run their applications on CNAMEd virtual hosts for their different services (for example, Google™ Google? run maps.google.com, images.google.com, etc.) This can cause problems, because many things that run on the servlet framework, Wicket included, construct URLs using absolute paths based on the context path that the app is deployed in.
...
Wicket 1.3 uses relative URLs, which lets it avoid these kind of problemsneatly avoids this problem in the first place. Don't use setContextPath with Wicket 1.3, unless you're running a PortletApplication.