First have a look at issue https://issues.apache.org/jira/browse/WICKET-4776. I've adapted the solution to preserve the port and the protocol in the UrlRender in our UrlRender subclass and at the first glance it might work. On my local developer machine running our webapplication on a Tomcat webserver the generated links to secure pages seem to be correct, e.g. requesting the Home Page Url http://localhost:8080/home.html now contains links to secure pages like https://localhost:8443/account.html with correct Urls. But running the same application on a Tomcat server with an Apache Http Server (with an AJP connector and the default ports 80/443) results in wrong rendered Https links. The Home Page with the Url http://domainname.com/home.html now contains the wrong link https://domainname.com:80/account.html. I reckon the preserved Http port (Http port 80) leads to this problem. I'm not sure, whether a prober solution would be to check the HTTP header first. If the HTTP header contains a port, preserve it, otherwise not.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UrlRenderer-renders-wrong-HTTPS-links-tp4653054.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
