[jetty-discuss] [jira] Updated: (JETTY-197) AJP13Connector & HttpServletRequest.getRemoteHost()

[Leopold A. (JIRA) <ji...@co...>]

     [ http://jira.codehaus.org/browse/JETTY-197?page=all ]

Leopold Agdeppa updated JETTY-197:
----------------------------------

    Attachment: ajppatch.patch

fix

> AJP13Connector & HttpServletRequest.getRemoteHost()
> ---------------------------------------------------
>
>                 Key: JETTY-197
>                 URL: http://jira.codehaus.org/browse/JETTY-197
>             Project: Jetty
>          Issue Type: Bug
>         Environment: Jetty HEAD
> Apache 1.3.x w/mod_jk (Debian stable - 'sarge') behind NAT forwarding to Jetty (TRUNK as of Saturday 9/12/06)
>            Reporter: Russell Howe
>         Assigned To: Leopold Agdeppa
>         Attachments: ajppatch.patch
>
>
> The behaviour of getRemoteHost() when using the AJP13Connector has changed since Jetty 5.0.0.
> Host A (UA) -- HTTP request --> Host B (Apache) --- AJP13 request ---> Jetty (AJP13)
> In 5.0.0, getRemoteHost() returned the address of the client behind the AJP13 host (i.e. host A in the above)
> In current Jetty, getRemoteHost() returns the address of the Apache server (which is the client as far as Jetty is concerned, I suppose...)
> Is this behaviour intentional? It confuses the hell out of a few things here, which serve different content depending on which side of the NAT box the user is on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira