Enable web agent to handle Ajax 302 redirects to validate 3rd party cookie domain

Idea created by Guest on Aug 9, 2016
    Under review
    Score3
    • Amey.Govekar
    • JMCColorado
    • rminnj

    Applications that are entirely Web 2.0 Ajax based do not handle 302 redirects correctly. Currently the workaround is to adjust the webappclientresponse parameter so that the web agent is informed that an ajax call is being made and changes the response status code from 302 to 200.

     

    However once the SessionUpdatePeriod is reached, a call is made to the policy server to update the session in the cookieprovider domain. This then throws an XMLHTTPREQUEST Error that throws

     

    XMLHttpRequest cannot load. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin is therefore not allowed access

     

    There needs to be a way to account for Ajax requests that are made for applications utilizing 3rd party cookie domains.