Not in your struts app.
I've seen this in a production situation and it's usually a bug in the
proxy. If you can try setting up a NAT environment without the proxy and
then with the proxy, if the bug only occurs when the proxy is in place
then you know where the problem is.
Al.
P.S. The buggy proxy I encountered was Novell iChain, I don't know the
version, but after the customer put in a rule that the site the struts
app was on was not to be proxied everything worked and they were
satisfied they should be talking to Novell about the problem.
Julien ROTT wrote:
So there is no solution to avoid the sessions clash in this situation ?
2008/6/5 Dave Newton <[EMAIL PROTECTED]>:
--- On Thu, 6/5/08, Julien ROTT <[EMAIL PROTECTED]> wrote:
I guess the server is a bit confused because the clients
have the same IP address (I tried jboss and jetty).
Session management isn't really handled by Struts, it's handled via the app
server and browser (by sending the session id cookie).
AFAIK the requesting IP address doesn't (shouldn't?) have anything to do
with it, it's all about what the browser sends to identify the session.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
