RequestEvents Class

Holds events that allow performing of custom logic at specific points within the request processing.

Inheritance Hierarchy

System.Object
  CMS.Base.RequestEvents

Namespace: CMS.Base
Assembly: CMS.Base (in CMS.Base.dll) Version: 13.0.131

Syntax

public sealed class RequestEvents

The RequestEvents type exposes the following members.

Fields

	Name	Description
Public field Static member	AcquireRequestState	Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request.
Public field Static member	Authenticate	Occurs when a security module has established the identity of a user.
Public field Static member	Authorize	Occurs when a security module has verified user authorization.
Public field Static member	Begin	Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request.
Public field Static member	End	Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request.
Public field Static member	Finalize	Occurs as the last event in the pipeline and can be used to clean up and release resources used by the request.
Public field Static member	LogRequest	Occurs just before ASP.NET performs any logging for the current request.
Public field Static member	MapRequestHandler	Occurs when a handler is selected to respond to the request.
Public field Static member	PostAcquireRequestState	Occurs after the request state (for example, session state) that is associated with the current request has been obtained.
Public field Static member	PostAuthenticate	Occurs when a security module has established the identity of the user.
Public field Static member	PostAuthorize	Occurs when the user for the current request has been authorized.
Public field Static member	PostLogRequest	Occurs when ASP.NET has completed processing all the event handlers for the LogRequest event.
Public field Static member	PostMapRequestHandler	Occurs after ASP.NET has mapped the current request to the appropriate event handler.
Public field Static member	PostReleaseRequestState	Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored.
Public field Static member	PostRequestHandlerExecute	Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution.
Public field Static member	PostResolveRequestCache	Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache.
Public field Static member	PostUpdateRequestCache	Occurs when ASP.NET finishes updating caching modules and storing responses that are used to serve subsequent requests from the cache.
Public field Static member	Prepare	Occurs before the Begin event.
Public field Static member	PreRequestHandlerExecute	Occurs just before ASP.NET starts executing an event handler.
Public field Static member	PreSendRequestContent	Occurs just before ASP.NET sends content to the client.
Public field Static member	PreSendRequestHeaders	Occurs just before ASP.NET sends HTTP headers to the client.
Public field Static member	ReleaseRequestState	Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data
Public field Static member	RequestCompleted	Occurs when the managed objects that are associated with the request have been released.
Public field Static member	ResolveRequestCache	Occurs when ASP.NET finishes an authorization event to let the caching modules serve requests from the cache, bypassing execution of the event handler (for example, a page or an XML Web service).
Public field Static member	RunEndRequestTasks	Occurs after the End event has finished.
Public field Static member	UpdateRequestCache	Occurs when ASP.NET finishes executing an event handler in order to let caching modules store responses that will be used to serve subsequent requests from the cache.

Remarks

These request events allow you to handle most usable events from application without the need to create a custom HTTP module or edit global.asax.

The events are represented by fields of the SimpleHandler type. Handler methods need to be assigned to the Execute event of individual fields.

The events are not raised out of web-based applications without the CMSApplication module (when using the Kentico API externally).