Previous Topic: Prevent Session Cookie Creation or Updates

Next Topic: Set Secure Cookies

Prevent Session Cookie Creation or Updates Based on Method and URI

Some Web applications, such as Microsoft Outlook Web Access, make HTTP requests behind the scenes even when a user is not actively using the application. For example, the Web Access application makes HTTP requests even when the user is not actively checking for new email on the server.

These requests update the SMSESSION cookie so that the session never expires, even though the user has been idle. You can prevent the Web Agent from creating or updating session cookies during these background requests so that sessions expire typically.

To prevent creation or updates based on method and URI

  1. Set all the following parameters:
    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.

    Default: No default

    OverlookSessionForMethodUri

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

    Default: No default.

    Limits: Specify a relative URI

    Example: POST, /directory/file prevents updates to the SMSESSION cookie for POST requests to /directory/resource.

    Note: Methods are processed before URIs.