Represents the processing context for global-level operations.
The following table lists the methods exposed by the IHttpServer interface.
Adds an HTTP_DATA_CHUNK structure to the cache.
Associates an asynchronous completion operation with the thread pool.
Decrements the thread count for the thread pool.
Returns a context container that may be dispensed.
Performs a specific cache operation.
Flushes the kernel cache for a specific Uniform Resource Identifier (URI).
Retrieves the name of the application pool for the current request.
Retrieves the configuration object for the current context.
Returns an IHttpFileInfo interface for a specific file path.
Retrieves the managed type for a specific site and Uniform Resource Identifier (URI).
Retrieves an IHttpPerfCounterInfo interface.
Retrieves a custom interface for a protocol manager.
Retrieves an IHttpTraceContext interface.
Retrieves an IWpfSettings interface.
Increments the thread count for the thread pool.
Tests whether the worker process was launched from the command line.
Triggers a notification that a configuration path has changed.
Raises a custom global-level notification.
Triggers a notification that a file has changed.
Retrieves a specific fragment from the cache.
Recycles an application.
Recycles the worker process that is handling the current request.
Registers file-change notification for a particular directory.
Removes a specific fragment from the cache.
Reports the worker process as unhealthy.
Determines whether a specific precondition has been met for the current request.
Represents the processing context for global-level operations, and enables retrieving configuration files, extended interfaces, metadata, tokens, and the worker process framework.
The IHttpServer interface represents the main programmatic interface for HTTP modules to access information about the current global-level context. This interface retrieves several additional interfaces that you can use when you write HTTP modules. For example, the GetFileInfo and GetPerfCounterInfo methods retrieve, respectively, the IHttpFileInfo and IHttpPerfCounterInfo interfaces for the global context. These interfaces allow developers to retrieve a file interface for a specific file, or an interface for the performance counters.
IIS 7 allows developers to restart an application, restart a worker process, or report the current context as unhealthy. This functionality is exposed, respectively, through the RecycleApplication, RecycleProcess, and ReportUnhealthy methods.
The IHttpServer interface provides several methods that allow developers to manipulate the IIS cache. These methods are the AddFragmentToCache, DoCacheOperation, FlushKernelCache, ReadFragmentFromCache, and RemoveFragmentFromCache methods.
Http.sys manages and owns the fragment cache. At any time, Http.sys may override or delete information that you directed to be stored. There is currently no way to lock information in the fragment cache as nonvolatile information.
Developers can use the GetAppPoolName, GetManagedType, GetWorkerProcessSettings, and SatisfiesPrecondition methods to retrieve information from the configuration settings for the current context.
The IHttpServer interface also provides the NotifyConfigurationChange, NotifyFileChange, NotifyCustomNotification methods, which allow developers to raise notifications for configuration changes, file changes, or a custom notification condition, respectively.
IIS 7.0, IIS 7.5, IIS Express 7.5, IIS 8.0