tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
Date Wed, 10 Aug 2011 16:37:39 GMT
Hash: SHA1


On 8/9/2011 4:49 PM, Rainer Jung wrote:
> On 09.08.2011 20:45, Lataxes, Karl wrote:
>> Our clients cannot send or process JSESSIONIDs as they are not web 
>> browsers, but proprietary equipment running embedded software that 
>> sends HTTP POST messages to a servlet on our internal network.
>> The servlet keeps track of sessions internally by assigning a
>> session id which is contained within the HTTP request body.
>> I believe my best solution would be to send an additional header 
>> containing the session id with the servlet response and using that 
>> for sticky sessions.  I am working with our embedded software 
>> developers on sending this header back to the servlet during 
>> subsequent client requests to facilitate sticky sessions.  I know
>> I will probably have to go to Apache 2.2 to accommodate this, but
>> that was something I expected.
> Are you aware of the fact, that a cookie *is* an additional HTTP
> header, namely the header named "Cookie"? So if you can set HTTP
> headers to values you can define, then you *can* send cookies.


To Karl: I don't think any of your questions are stupid. You're just
trying to solve a problem that's complicated. We are trying to coax a
solution out of the situation :)

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message