Online Book Reader

Home Category

Programming Microsoft ASP.NET 4 - Dino Esposito [39]

By Root 5258 0

Configures the Session object.

Machine, application

Defines settings used to support the navigation infrastructure.

Everywhere

Configures the tracing system.

Machine, application

Defines the default trust level.

Machine, application

Defines routes mapping a requested URL to a real page.

Everywhere

Locates client scripts.

Everywhere

Managed Web Parts.

Everywhere

Configures Web services. The Web Services technology is considered obsolete, as is this section.

Everywhere

Defines settings for XHTML conformance.

Each of the elements listed in Table 3-3 features its own schema and provides attributes and enumerations to pick values from.

In addition to the sections listed in Table 3-3, the group contains a subgroup named . Table 3-4 lists the child elements.

Table 3-4. Sections Allowed Within

Section

Overridable

Description

Machine, application

Configures the global cache settings for an ASP.NET application.

Machine, application

Configures the output cache for a Web application.

Machine, application

Defines caching profiles.

Machine, application

Configures the SQL cache dependencies for an ASP.NET application.

Let’s examine some of the aforementioned sections in a bit more detail. For a complete reference, though, you might want to check out the excellent MSDN online documentation starting at http://msdn.microsoft.com/en-us/library/b5ysx397.aspx.

The Section


Anonymous identification is a feature that assigns a predefined identity to users who connect anonymously to an application. Anonymous identification has nothing to do with the anonymous user you can set at the IIS level, nor does it affect the authentication mechanism of ASP.NET. The feature is designed to work with the user profile API to simplify the way you write code in scenarios where both authenticated and unauthenticated users can use the site.

The section allows you to configure how it works. Here’s the overall schema of the section:

enabled="[true | false]"

cookieless="[UseUri | UseCookies | AutoDetect | UseDeviceProfile]"

cookieName=""

cookiePath=""

cookieProtection="[None | Validation | Encryption | All]"

cookieRequireSSL="[true | false]"

cookieSlidingExpiration="[true | false]"

cookieTimeout="[DD.HH:MM:SS]"

domain="cookie domain"

/>

Basically, anonymous identification creates a cookied or cookieless ticket and associates it with the ongoing request. The enabled attribute turns the feature on and off; the cookieless attribute instructs the ASP.NET runtime about cookie usage. Table 3-5 illustrates the options for the cookieless attribute.

Table 3-5. Options for the cookieless Attribute

Value

Description

AutoDetect

Uses cookies if the browser has cookie support currently enabled. It uses the cookieless mechanism otherwise.

UseCookie

Always uses cookies, regardless of the browser capabilities.

UseDeviceProfile

Uses cookies if the browser supports them, and uses the cookieless mechanism otherwise. When this option is used, no attempt is made to check whether cookie support is really enabled for the requesting device. This is the default option.

UseUri

Never uses cookies, regardless of the browser capabilities.

All other attributes relate to the cookie, if one gets created. You can set its name—the default name is .ASPXANONYMOUS—as well as its path, domain, protection, expiration, and timeout. You can also indicate whether Secure Sockets Layer (SSL) should be used to transmit the cookie.

The Section


The section allows you to configure a Web site for various types of user authentication, including Forms authentication as well as Passport and IIS-driven authentication. This section has two mutually exclusive subsections— and

Return Main Page Previous Page Next Page

®Online Book Reader