This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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?
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.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com