posted 21 years ago
Well i have had that problem before ..
the session context is based on the Server "the browser sees"
sine the session is saved on a cookie called jsessionid this cookie is set to act on the context of the Server name .
that's why the context in localhost and yourmachinename.com are different..
also if you try autentications ( that is also a cookie ) are based on the same schema
Maybe it could be possible; if needed, to pass along the session ID to have the same context.
Grettings .