Page History

...

That servlet container is fed requests through a Apache HTTPD the mod_proxy_http module.

Apache HTTPD connects to the client using HTTPS and that HTTPS is configured to serve clients using HTTPS, which is terminated at the HTTPD server before it is forwarded tot the servlet container.

The servlet container knows nothing about the fact that HTTPS is used so each redirect that is generated will look like http://servername.com/someuri^{Image Removed} instead of https://servername.com/someuri^{Image Removed}.

Therefore the Header directive in a configuration file for Apache HTTPD is typical in Apache HTTPD for a wicket application running in a servlet container behind Apache:

...

This is useful if all of your application must be served over HTTPS.
Wicket has some facilities for HTTPS but that is useful only if some but not all of your pages must be served over HTTPS.