Web Agent :: Ajax Integration : HTML Post Preservation Page

Document ID : KB000050349
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

The HTML Post Preservation page is sent to my browser which is an AJAX application that does not understand standard HTML code, and thus, my AJAX browser cannot get further in browsing. How can I solve this issue?

Solution:

HTML Post Preservation page needs the browser to be able to understand standard HTML data. Web Agent are designed to work with standard HTML protocol.

The message from the Web Agent for Post Preservation will be returned to the program that made the POST request so in your case it would be sent back to the AJAX application. The Post Preservation mechanism is designed for browsers and therefore any non browser such as AJAX has to be able to handle the HTTP requests that are sent back to it and perform the correct actions like your browser would.

The solution for that problem is to modify the AJAX browser to handle HTML code properly.

As a workaround:

  1. Follow the technote described here :

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec458941.aspx

    and try to avoid the Post Preservation call by managing the SessionGracePeriod.

  2. You can also check the following ACO parameter, which might stop cookie updates based on the URI and the method:

    OverlookSessionForMethods

    Specifies whether the Web Agent compares the request method of all HTTP requests against the methods listed in this parameter.
    If a match occurs, the Web Agent does not create or update an SMSESSION cookie. Also, cookie providers (if configured) are not updated for that request.
    eg: GET or POST

    OverlookSessionForMethodUri

    Specifies whether the Web Agent compares the URI from all HTTP requests against the URI listed in this parameter. If a match occurs, the Web Agent does not create or update an SMSESSION cookie. Also, cookie providers (if configured) are not updated for that request.
    Default: No default.

    OverlookSessionForUrls

    Specifies whether the Web Agent compares the URLs from all HTTP requests against the URLs listed in this parameter. If a match occurs, the Web Agent does not create or update an SMSESSION cookie. Also, cookie providers (if configured) are not updated for that request.
    Default: No default

    Example: Use a relative URL, such as /MyDocuments/index.html.
    Do not use an absolute URL
    (http://fqdn.host/MyDocuments/index.html)

    (Web Agent Configuration Guide r12.0 SP3)

Note: There are some other issues reported with integration of AJAX with Web Agent:

  • Session timeout problems:

  • Ajax does not handle cross domain redirect properly;

  • Some of the PostPreservationData issue faced with Ajax integration have been solved by setting : PresevePostData=No and legacycookieprovider=yes