We have an application that makes a large number of AJAX calls to display report data to the user. These calls fail when the client receives a 302 to the cookieprovider. It is not practical to use the OverLookSessionForMethodsURI or URL parameters in this case because of the number of resources that exist.
Has anyone had success implementing the new ACO parameter WebAppClientResponse in a r12.5 agent? Will this address prevent the session creation/update issue we have with this application?
Thanks,
Jeff