Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] jetty, Vaadin, mod_proxy and absolute local URIs?

the ForwardedRequestCustomizer will utilize information from the proxy (mod_proxy in your case) to set the server name and server port to the correct pre-proxy values.

However, it requires that the proxy include the various X-Forwarded-* headers (there are several) in the request headers that it sends to Jetty.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Tue, Jan 13, 2015 at 3:30 AM, Kristian Rink <kawazu428@xxxxxxxxx> wrote:
Folks;

we run a Vaadin 6.x application with an embedded Jetty behind an apache2 mod_proxy reverse proxy setup. The mod_proxy/jetty setup is something we're fairly familiar with, and it works well out of the box for most of our applications.

However, talking about the Vaadin applications, it seems to fail in some situations whenever Vaadin internally tries to guess server name and port using ServletRequest.getServerName() / .getServerPort() and ends up with name and port of the server instead of the proxy.

There seem to be some tickets for Vaadin, in example

http://dev.vaadin.com/ticket/4131 ,

but I fail to really work around this. Is there anything I can do about this, Jetty-wise? So far I introduced a ForwardedRequestCustomizer to my (embedded) Jetty configuration, but this doesn't change much about this particular behaviour. Any hints on that greatly appreciated... :/

TIA and all the best,
Kristian
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top