Versions Compared

Old Version 5

changes.mady.by.user Alastair Maw

Saved on

compared with

New Version 6

changes.mady.by.user Unknown User (victori)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: critical configuration option to get everything working correctly with apache.

...

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 neatly avoids this problem in the first place. Don't use setContextPath with Wicket 1.3, unless you're running a PortletApplication.

For recent versions of Apache 2.2 and up you might want to add the following to get Authorized wicket sessions working correctly. This only applies to wicket 1.3 and up.

Code Block

ProxyPassReverseCookiePath /ordering /