Installation and Upgrade Guides › Web Agent Installation Guide › Upgrade a Web Agent to r6.0 SP6 › How to Prepare for a Web Agent Upgrade › Cookie Provider Redirection Differences Between 4.x and 6.x Agents

Previous Topic: Ensure LD_PRELOAD Variable Does Not Conflict with Existing Agent

Next Topic: Replace Existing Read-only Files
Cookie Provider Redirection Differences Between 4.x and 6.x Agents

6.x Web Agents redirect to the cookie provider on GET and POST actions, whereas 4.x Web Agents redirect to the cookie provider only on GET actions. This functional difference causes upgrade issues when applications that require cookie provider support for GET actions and Web services responding to POST actions are installed on IIS virtual servers.

All traditional 6.x Web Agents (not the framework agents) have been modified to redirect to the cookie provider only for GET actions. New and rearchitected framework agents continue to redirect to the cookie provider for GET and POST actions so Web Agents can support POST preservation when a cookie provider is enabled.

Note: For more information on Framework agents, see the Web Agent Guide.

Web service applications or any custom application that cannot interpret 302 redirects should be configured separately from applications requiring multi-cookie domain single sign-on. Clients using Web services should consider moving these applications to servers separate from their other applications that require multi-cookie domain single sign-on.