Hi,
I think you should ask in Tomcat mailing lists.
The related code in Wicket is:
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/protocol/http/servlet/ServletWebResponse.java?source=cc#L232
As you can see Wicket always passes relative url to the
you could use proxyPort“ in your connector configuration, but this will always
override ‚getServerPort‘ with this value no matter you’ve a http or https
request.
Do you use an apache or nginx in front?
Am 12.12.2013 um 05:05 schrieb Matthew Welch matt...@welchkin.net:
I'm sure I'm missing
That makes sense. I'll ask there. Thank you.
Matt
On Thu, Dec 12, 2013 at 2:00 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
I think you should ask in Tomcat mailing lists.
The related code in Wicket is:
We are considering something along those lines you are suggesting as an
alternative.As far as load balancers, we actually have two separate
situations: one uses AWS Elastic Load Balancer and the other HAProxy.
Matt
On Thu, Dec 12, 2013 at 4:35 AM, Michael Haitz michael.ha...@1und1.dewrote:
I'm sure I'm missing something simple as there are certainly many others
using similar setups, but I cannot figure out what I'm doing wrong.
We force all requests from the public internet to use HTTPS when accessing
our app.We terminate SSL at the load balancer and the request that actually
hits
