Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
MIME-Version: 1.0
In-Reply-To: <86fff4d4-9195-53cf-65d6-f006c2b8f892@apache.org>
References: <CA+bGTTSwP12StzX4_TYOizkVi1MkM=pxMv4bXrHJnTqjHmLvfg@mail.gmail.com>
 <86fff4d4-9195-53cf-65d6-f006c2b8f892@apache.org>
From: Nick Johnson <nick@bluejeansnet.com>
Date: Sun, 5 Mar 2017 10:37:12 -0800
Message-ID: <CA+bGTTRfPu1Ggy3wnHpp6eQWSQXik1XSA3_5jfG=zK4B83LFTQ@mail.gmail.com>
Subject: Re: Handling wildcard domains in Tomcat 8.0
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a1143f0ec40079a054a0011df
archived-at: Sun, 05 Mar 2017 18:45:11 -0000

--001a1143f0ec40079a054a0011df
Content-Type: text/plain; charset=UTF-8

On Mar 5, 2017 9:50 AM, "Mark Thomas" <markt@apache.org> wrote:

On 04/03/17 04:33, Nick Johnson wrote:
> Greetings,
>
> I have observed that with the default configuration where the <Host> name
> is 'localhost', Tomcat will change the Host and X-Forwarded-Host headers
to
> the IP address of the local machine.

That is not correct. Tomcat makes no changes to the Host or
X-Forwarded-Host header it receives in the default configuration.


Are there any configuration modifications that could cause this behavior to
manifest?

Running nc or tcpdump on the command line, I see the correct Host and
X-Forwarded-Host headers arriving for Tomcat, but from my application, the
Host header and X-Forwarded-Host header both contain the IP address of the
local machine.

Using the same war file in a different container (Jetty), I do not observe
this behavior.

I also do not observe this behavior if the Host header matches either the
<Host> name or an <Alias> name.

   Nick

--001a1143f0ec40079a054a0011df--