Re: [jetty-users] NAT with HTTP 1.0 returns internal IP address

["martijn.list" <martijn.list@xxxxxxxxx>]

On 04/08/2013 06:05 PM, Simone Bordet wrote:
> Hi,
>
> On Mon, Apr 8, 2013 at 5:15 PM, Simone Bordet <sbordet@xxxxxxxxxxx> wrote:
> > Martijn,
> >
> > On Mon, Apr 8, 2013 at 10:47 AM, martijn.list <martijn.list@xxxxxxxxx> wrote:
> > > Connect with telnet to a Jetty server on port 89 (in this example I use
> > > www.webtide.com) issue a GET with the HTTP 1.0 protocol:
> > >
> > > telnet www.webtide.com 80
> > >
> > > Trying 72.32.76.94...
> > > Connected to www.webtide.com.
> > > Escape character is '^]'.
> > > GET index.html HTTP/1.0
> > >
> > > HTTP/1.1 302 Found
> > > Location: https://192.168.100.94:443index.html
> > > Content-Length: 0
> > > Server: Jetty(9.0.1-SNAPSHOT)
> > >
> > > Connection closed by foreign host.
> > >
> > >
> > > The Location header in the HTTP response tells me to connect to an internal
> > > IP address 192.168.100.94. There are two problems with this:
> >
> > So I tried and I can reproduce; if I use HTTP 1.1, then I get the
> > correct Location header.
> > Reproducible test cases make miracles in reply speed :)
> >
> > Seems a bug, investigating.
>
> What Jetty version, BTW ?

I'm using Jetty 8 but I think the problem occurs with all Jetty versions.

> We can handle this in Jetty 9 by adding a secureHost property to
> HttpConfiguration (along with already existing securePort and
> secureScheme).

But isn't this only for SSL?

Kind regards,

Martijn Brinkers