URL Request Outcomes

  • Article

This section and the subsequent sections describe the possible outcomes when a user requests a URL. Internet Information Services (IIS) detects the request sent by the browser and notifies the AuthFilter of the SF_NOTIFY_PREPROC_HEADERS event. At this time, the AuthFilter takes control of processing the request and performs the following actions:

  1. Checks for site configuration properties in the local site configuration cache and, if not found, reads the site configuration properties from the Administration database using a SiteConfig object and stores them in the local site configuration cache.

  2. Checks whether the URL is correct, automatically correcting for the case sensitivity of the IIS virtual directory roots.

  3. Checks for session-cookie support on the browser.

At this point, three actions are possible. The user is redirected to either a support page or a login page, or the user is sent the requested URL.

This section contains:

  • Case 1: Redirect to a Support Page. Describes the actions of the AuthFilter when session-cookie support is disabled.

  • Case 2: Send the Requested URL. Describes the actions of the AuthFilter when cookies are enabled and the requested URL has anonymous access rights, or the user has access rights to the requested URL and the returned cookie contains a valid MSCSAuth ticket.

  • Case 3: Redirect to a Login Page. Describes the actions of AuthFilter that lead to the user being redirected to a login page.


All rights reserved.