-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rainer,
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. +1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5Cs9MACgkQ9CaO5/Lv0PB+/QCeJL4+sjYbPf2C25cyOo6UO6k2 lt8AoK74fgDDcXmv3KW76tvw8e/mjqg3 =Z99M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
