Occurs when ASP.NET acquires the current state (for example, session state) that is associated with the current request.

Occurs when a security module has established the identity of the user.

Occurs when a security module has verified user authorization.

Occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request.

Occurs when the application is disposed.

Occurs as the last event in the HTTP pipeline chain of execution when ASP.NET responds to a request.

Occurs when an unhandled exception is thrown.

Occurs just before ASP.NET performs any logging for the current request.

Occurs when the handler is selected to respond to the request.

Occurs when the request state (for example, session state) that is associated with the current request has been obtained.

Occurs when a security module has established the identity of the user.

Occurs when the user for the current request has been authorized.

Occurs when ASP.NET has completed processing all the event handlers for the LogRequest event.

Occurs when ASP.NET has mapped the current request to the appropriate event handler.

Occurs when ASP.NET has completed executing all request event handlers and the request state data has been stored.

Occurs when the ASP.NET event handler (for example, a page or an XML Web service) finishes execution.

Occurs when ASP.NET bypasses execution of the current event handler and allows a caching module to serve a request from the cache.

Occurs when ASP.NET finishes updating caching modules and storing responses that are used to serve subsequent requests from the cache.

Occurs just before ASP.NET starts executing an event handler (for example, a page or an XML Web service).

Occurs just before ASP.NET sends content to the client.

Occurs just before ASP.NET sends HTTP headers to the client.

Occurs after ASP.NET finishes executing all request event handlers. This event causes state modules to save the current state data.

Occurs when the managed objects that are associated with the request have been released.

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).

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.