There is a problem in the current session-based architecture due to which sessions of different users are getting mixed up on client side when client set session_maintain_property = true
BindingProvider bp = (BindingProvider)port; bp.getRequestContext().put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true); so client always send JSESSIONID back to server, is always the last session on client side. JIRA [EMAIL PROTECTED] wrote: > > SESSION_MAINTAIN_PROPERTY doesn't track cookies other than JSESSIONID > --------------------------------------------------------------------- > > Key: CXF-966 > URL: https://issues.apache.org/jira/browse/CXF-966 > Project: CXF > Issue Type: Bug > Components: Transports > Affects Versions: 2.0.1, 2.1 > Reporter: Joe Sunday > > > When using CXF as a client, SESSION_MAINTAIN_PROPERTY only tracks the > session id from the server if the cookie is named JSESSIONID. It does not > track the session id if the server is using a different cookie name. > > It should track all Set-Cookie headers from the server. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > -- View this message in context: http://www.nabble.com/Created%3A-%28CXF-966%29-SESSION_MAINTAIN_PROPERTY-doesn%27t-track-cookies-other-than-JSESSIONID-tp12456478p18528230.html Sent from the cxf-issues mailing list archive at Nabble.com.
