Sessions and the Event Model

The HttpApplication object raises a series of events during the life of the HTTP protocol request:

❑ BeginRequest: This event fires at the beginning of every request.
❑ AuthenticateRequest: This event is used by the security module and indicates that arequest
is about to be authenticated. This is where the security module, or you, determines who the user is.
❑ AuthorizeRequest: This event is used by the security module and indicates that a request is about to be authorized. This is where the security module, or you, determines what the user is
allowed to do.
❑ ResolveRequestCache: This event is used by the caching module to determine whether this now-authorized request can bypass any additional processing.
❑ AcquireRequestState: This event indicates that all session state associated with this HTTP
request is about to be acquired.
❑ PreRequestHandlerExecute: This is the last event you get before the HttpHandler class for
this request is called.
❑ PostRequestHandlerExecute: This is the event that fires just after the HttpHandler is called.
❑ ReleaseRequestState: Indicates that the session state should be stored. Session state is persisted
at this point, using whatever Session-state module is configured in web.config.
❑ UpdateRequestCache: All work is complete, and the resulting output is ready to be added to the cache.
❑ EndRequest: This is the last event called during a request.