AnsweredAssumed Answered


Question asked by harshit.verma on Aug 29, 2016
Latest reply on Aug 30, 2016 by harshit.verma

We have a domain with only one realm protecting '/eserve/agentEnquiry/'. Application was reporting 302 errors when AJAX calls were made. To overlook session update we used the below ACO parameters:

OverlookSessionForUrls /eserve/agentEnquiry

OverlookSessionAsPattern yes


But, we couldn't make this approach work. The application still reported 302 for ajax calls. We were able to make it work by specifying individual URLs instead of pattern matching.


Can anyone please help us figure out why the pattern matching approach is not working?