Application Lifecycle

 

0	APPLICATION_START
1	BeginRequest	ASP.NET HTTP pipeline begins to work on the request
2	AuthenticateRequest	All the internal ASP.NET auhentication modules subscribe to this event. If no authentication module module produced an authenticated user, an internal default authentication module is invoked to produce an identity for the unauthenticated user
3	PostAuthenticateRequest	Post authentication, all the information is stored in the HttpContext User property
4	AuthorizeRequest	Event commonly handled by application code based on business logic or other application requirements
5	PostAuthorizeRequest	The request has been authorized
6	ResolveRequestCache	ASP.net runtime verifies whether returning a previously cached page can resolve the request If a valid cached representation is found, the request is served from cache, and calls the EndRequest handlers
7	PostResolveRequestCache	If request can not be served from the cache, and the procedure continues An Http handler corresponding to the requested URL is created at this point. A .aspx page will cause an instance of Page class to be generated
8	PostMapRequestHandler	Event fires once HttpHandler gets created
9	AcquireRequestState	Module associated to this event tries to retrieve state information from the request
10	PostAcquireRequestState	The state information (session/application) has been acquired
11	PreRequestHandlerExecute	Fired immidiately prior to executing the handler for a given request
12	PostRequestHandlerExecute	Event is raised when the handler has generated the response text
13	ReleaseRequestState	Event raised when handler releases the state information and prepares to shut down. Also used by the session state module to update the dirty session state if necessary
14	PostReleaseRequestState	The updated state is persisted
15	UpdateRequestCache	ASP.net runtime determines whether the generated output, now also properly filtered by registered modules, should be cached to be reused with upcoming idnetical requests
16	PostUpdateRequestCache	The page has been saved to the output cache if it was configured to do so
17	EndRequest	Final step in HTTP pipeline. The control passes back to the HttpRuntime object, which is responsible for the actual forwarding of the response to the client
0	APPLICATION_END