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
From: Enrico Olivelli <eolivelli@gmail.com>
Date: Fri, 3 Nov 2017 13:18:53 +0100
Message-ID: <CACcefgfs5Uvs9Rz1Mqny5nhU-G=EuxFe+EUG31Xu6KdOeFFXNA@mail.gmail.com>
Subject: HttpServletRequest in AsyncContext does not handle X-Forwarded-For (RemoteIpValve)
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary="001a114204f2b9fda4055d131b16"
archived-at: Fri, 03 Nov 2017 12:19:00 -0000

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

Hi,
I am running a servlet and I get strange result for
HttpServletRequest#getRemoteAddr().

I have configured RemoteIpValve which handles the X-Forwarded-For header
and replaces the original IP address with the value contains in such header.

I have an HttpServlet which dispacts the execution to a custom threadpool
and uses request.startAsync()

It seems that if I call getRemoteAddr on the original HttpServletRequest
the value for getRemoteAddr() is correct, it contains the value of
X-Forwarded-For header.
When I call getRemoteAddr after calling startAsync() the result is the
original IP address of the request.

A workaround is to capture the IP Address early but I wonder if I am
missing something, if it is an expected behavior or if I should file an
issue.

I am using tomcat 8.5.15


Thanks
Enrico

--001a114204f2b9fda4055d131b16--