• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

IBM HTTP Server Session Affinity

 
Thad Smith
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a question about how IBM HTTP Server performs session affinity using the default plugin-cfg.xml generated by WebSphere. If a request is generated with a jsessionid URL param (e.g. http://someurl.com/app?jsessionid=abc) and a JSESSIONID cookie, which takes precedence? The cookie or the URL param?
 
Xusheng Gong
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the infocenter, 'Enabling cookies takes precedence over URL rewriting. '

http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Fuprs_rsession_manager.html
 
Thad Smith
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Xusheng,

Thanks for the information. This article covers how WebSphere uses the JSESSIONID for session management, not how IBM HTTP Server (specifically the WebSphere plug-in for IHS) uses the JSESSIONID for server affinity (sticky sessions). I suspect that IHS prefers the cookie over the URL param the same way, but I haven't found any documentation that states this definitively.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic