On 11.03.2009 22:22, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rainer,
On 3/11/2009 5:06 PM, Rainer Jung wrote:
No, because [mod_jk] tries to act transparent by default, so it passes the
original client/server situation to Tomcat and Tomcat patches it's
client and server data inside the AJP connector in order to present the
webapp the situation like it was at the web server.
So, the REMOTE_ADDR environment variable is passed-through as... what?
If mod_jk tries to appear invisible, then the value of the REMOTE_ADDR
environment variable should be that of the original client (or, at
least, the original client as far as httpd is concerned).
See below.
Your previous message seems to say that mod_jk will provide the IP
address of the server running httpd as the REMOTE_ADDR when seen by Tomcat.
I can't read that out of my previous message. Could you please cite the
statement where I wrote that.
So, which is it?
I was not talking about CGI environment variables. mod_jk will not pass
any environment variables, because they don't exist.
If you use the CGI servlet of Tomcat, then Tomcat will set an
environment variable REMOTE_ADDR to the value of request.getRemoteAddr().
And as I said getRemoteAddr() will be the address of the web server
client, unless you played with configuration.
Caution: there is yet another possible set of data, namely request
attributes. Those are neither headers nor CGI env vars. Just so that
there is still another reason for confusion.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
