On Fri, Mar 27, 2009 at 5:43 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
> On 27.03.2009 01:21, Michael B Allen wrote:
>>
>> On Mon, Mar 23, 2009 at 10:38 AM, Michael B Allen<iop...@gmail.com>
>> wrote:
>>>
>>> On Mon, Mar 23, 2009 at 3:41 AM, Rainer Jung<rainer.j...@kippdata.de>
>>> wrote:
>>>>
>>>> Others might have better ideas, but as mentioned in the previous thread,
>>>> you
>>>> can forward the remote port with
>>>>
>>>> JkEnvVar REMOTE_PORT
>>>>
>>>> and retrieve it in Tomcat with
>>>>
>>>> request.getAttribute("REMOTE_PORT")
>>>>
>>>> Doesn't that work?
>>>
>>> Yes, it sounds like precisely what I'm looking for. I just didn't
>>> understand the significance of your previous message. I never used
>>> mod_jk before so I'll have to look into this JkEnvVar thing.
>>
>> Now I have someone using the ISAPI filter in IIS with Tomcat who is
>> also seeing getRemotePort return -1.
>>
>> Is there a work-around for IIS?
>>
>> I've modified our code to look for the REMOTE_PORT attribute. Is there
>> a way to export the REMOTE_PORT attribute with the ISAPI filter?
>
> Not at the moment. I expect us to fix this with the next version (then by
> already activating it by default).
Is there an ETA on that?
Will the dll of the fixed version work with and provide the
REMOTE_PORT to an older installation of Tomcat?
If not, is there absolutely no way to come up with a unique connection
id for a request in Tomcat if it runs through the ISAPI filter?
Mike
--
Michael B Allen
Java Active Directory Integration
http://www.ioplex.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
