Rainer Jung wrote:
On 21.03.2009 14:12, Mladen Turk wrote:
I should read the entire logic before posting.
I missed it's an env var.
Sorry for the noise ;)
No problem at all. Better safe than sorry.
I just committed a change to TC trunk and backport proposals to pick up
the REMOTE_PORT env var for request.getRemotePort().
So we might think about forwarding REMOTE_PORT by default in JK 1.2.29.
See the note I added to 6.0 STATUS.
IMO we should prefix all those env vars either with AJP_ or like
you did already for some with JK_
Now, JK_ is fine, but the AJP_ is more intuitive because it
can be reused by mod_proxy_ajp as well.
Not sure, but those vars on Tomcat side should be
removed when processed so that they don't end up
in req attributes since they are protocol private,
and if the AJP protocol would support this they would
never be visible.
Regards
--
^(TM)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
