Click or drag to resize
RequestEvents Class
Holds events that allow performing of custom logic at specific points within the request processing.
Inheritance Hierarchy
SystemObject
  CMS.BaseRequestEvents

Namespace: CMS.Base
Assembly: CMS.Base (in CMS.Base.dll) Version: 13.0.131
Syntax
C#
public sealed class RequestEvents

The RequestEvents type exposes the following members.

Fields
  NameDescription
Public fieldStatic memberAcquireRequestState
Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request.
Public fieldStatic memberAuthenticate
Occurs when a security module has established the identity of a user.
Public fieldStatic memberAuthorize
Occurs when a security module has verified user authorization.
Public fieldStatic memberBegin
Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request.
Public fieldStatic memberEnd
Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request.
Public fieldStatic memberFinalize
Occurs as the last event in the pipeline and can be used to clean up and release resources used by the request.
Public fieldStatic memberLogRequest
Occurs just before ASP.NET performs any logging for the current request.
Public fieldStatic memberMapRequestHandler
Occurs when a handler is selected to respond to the request.
Public fieldStatic memberPostAcquireRequestState
Occurs after the request state (for example, session state) that is associated with the current request has been obtained.
Public fieldStatic memberPostAuthenticate
Occurs when a security module has established the identity of the user.
Public fieldStatic memberPostAuthorize
Occurs when the user for the current request has been authorized.
Public fieldStatic memberPostLogRequest
Occurs when ASP.NET has completed processing all the event handlers for the LogRequest event.
Public fieldStatic memberPostMapRequestHandler
Occurs after ASP.NET has mapped the current request to the appropriate event handler.
Public fieldStatic memberPostReleaseRequestState
Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored.
Public fieldStatic memberPostRequestHandlerExecute
Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution.
Public fieldStatic memberPostResolveRequestCache
Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache.
Public fieldStatic memberPostUpdateRequestCache
Occurs when ASP.NET finishes updating caching modules and storing responses that are used to serve subsequent requests from the cache.
Public fieldStatic memberPrepare
Occurs before the Begin event.
Public fieldStatic memberPreRequestHandlerExecute
Occurs just before ASP.NET starts executing an event handler.
Public fieldStatic memberPreSendRequestContent
Occurs just before ASP.NET sends content to the client.
Public fieldStatic memberPreSendRequestHeaders
Occurs just before ASP.NET sends HTTP headers to the client.
Public fieldStatic memberReleaseRequestState
Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data
Public fieldStatic memberRequestCompleted
Occurs when the managed objects that are associated with the request have been released.
Public fieldStatic memberResolveRequestCache
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 fieldStatic memberRunEndRequestTasks
Occurs after the End event has finished.
Public fieldStatic memberUpdateRequestCache
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.
Top
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).

See Also