This documentation is archived and is not being maintained.

HttpCapabilitiesSectionHandler Class

Assists in reading in the <browserCaps> section of a configuration file and creating an instance of the HttpBrowserCapabilities class that contains the capabilities information for the client browser.


Namespace:  System.Web.Configuration
Assembly:  System.Web (in System.Web.dll)

public class HttpCapabilitiesSectionHandler : IConfigurationSectionHandler

The HttpCapabilitiesSectionHandler type exposes the following members.

Public methodHttpCapabilitiesSectionHandlerInitializes a new instance of the HttpCapabilitiesSectionHandler class.

Public methodCreateCreates an instance of the HttpBrowserCapabilities class that contains the capabilities information for the client browser.
Public methodEquals(Object)Determines whether the specified Object is equal to the current Object. (Inherited from Object.)
Protected methodFinalizeAllows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)
Public methodGetHashCodeServes as a hash function for a particular type. (Inherited from Object.)
Public methodGetTypeGets the Type of the current instance. (Inherited from Object.)
Protected methodMemberwiseCloneCreates a shallow copy of the current Object. (Inherited from Object.)
Public methodToStringReturns a string that represents the current object. (Inherited from Object.)

The HttpCapabilitiesSectionHandler class and the corresponding <browserCaps> configuration section have been deprecated in the .NET Framework version 2.0. The preferred method for managing browser capabilities is through browser definition files that are compiled for use by the BrowserCapabilitiesFactory class. The goal of both configuration methodologies is to generate an instance of the HttpBrowserCapabilities class that can be accessed from the Browser property of the HttpRequest class.

Using the browser definition files to store browser capabilities affords advantages over the alternative. It offers improved performance because the browser definition information is parsed from the XML configuration file and compiled into a class ahead of time. The browser definition files are also easier to maintain:

  • The definitions are hierarchical, and thus rely less on regular expressions to determine the browser capabilities.

  • The definitions can be organized in multiple files, making them easier to manage.

  • The definitions can be defined at any level, either at the Machine.config level or a specific application level. This eliminates the need to copy the entire set of definitions for the purpose of overriding the capabilities for a specific browser.

.NET Framework

Supported in: 4, 3.5, 3.0, 2.0

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.