20.10.2014, 03:18
|
#18 |
|
Banned
|
Цитата:
Сообщение от Narayana
...А о том порядке, в котором модули грызут запрос.
…про порядок вызова модулей http://blogs.msdn.com/b/tmarq/archiv...onditions.aspx BEGIN_REQUEST AUTHENTICATE_REQUEST AUTHORIZE_REQUEST RESOLVE_REQUEST_CACHE MAP_REQUEST_HANDLER ACQUIRE_REQUEST_STATE PRE_EXECUTE_REQUEST_HANDLER EXECUTE_REQUEST_HANDLER RELEASE_REQUEST_STATE UPDATE_REQUEST_CACHE LOG_REQUEST END_REQUEST ASP.NET request-processing stages http://www.iis.net/learn/application...ation-with-iis Заметка 1: Integrated mode allows both managed and native modules to register for events in the IIS pipeline. Заметка 2: Think of ASP.NET in classic mode as a pipeline within a pipeline. BeginRequest. The request processing starts. AuthenticateRequest. The request is authenticated. IIS and ASP.NET authentication modules subscribe to this stage to perform authentication. PostAuthenticateRequest. AuthorizeRequest. The request is authorized. IIS and ASP.NET authorization modules check whether the authenticated user has access to the resource requested. PostAuthorizeRequest. ResolveRequestCache. Cache modules check whether the response to this request exists in the cache, and return it instead of proceeding with the rest of the execution path. Both ASP.NET Output Cache and IIS Output Cache features execute. PostResolveRequestCache. MapRequestHandler. This stage is internal in ASP.NET and is used to determine the request handler. PostMapRequestHandler. AcquireRequestState. The state necessary for the request execution is retrieved. ASP.NET Session State and Profile modules obtain their data. PostAcquireRequestState. PreExecuteRequestHandler. Any tasks before the execution of the handler are performed. ExecuteRequestHandler. The request handler executes. ASPX pages, ASP pages, CGI programs, and static files are served. PostExecuteRequestHandler ReleaseRequestState. The request state changes are saved, and the state is cleaned up here. ASP.NET Session State and Profile modules use this stage for cleanup. PostReleaseRequestState. UpdateRequestCache. The response is stored in the cache for future use. The ASP.NET Output Cache and IIS Output Cache modules execute to save the response to their caches. PostUpdateRequestCache. LogRequest. This stage logs the results of the request, and is guaranteed to execute even if errors occur. PostLogRequest. EndRequest. This stage performs any final request cleanup, and is guaranteed to execute even if errors occur. ASP.NET Application Life Cycle Overview for IIS 7.0 http://msdn.microsoft.com/en-us/libr...v=vs.100).aspx Execution order of modules in IIS7 http://www.ksingla.net/2006/06/execu...dules_in_iis7/ http://www.iis.net/learn/application...ation-with-iis Думаю что для вас самое интересное это Цитата:
If multiple modules subscribe to the same event and set the same priority, the module that is listed first in the system.webServer/modules section gets executed first. RQ_EXECUTE_REQUEST_HANDLER is different in this respect as it picks up the ordering from system.webServer/handlers section. Taking the example of StaticFile handler entry from default IIS configuration which looks like the following
<add name="StaticFile" path="*" verb="*" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" resourceType="Either" requireAccess="Read" /> IIS picks one handler for a request but each entry can have multiple modules executed which can appear as comma separated list as is the case for StaticFile handler. StaticFileModule, DefaultDocumentModule and DirectoryListingModule, all three subscribe to RQ_EXECUTE_HANDLER and use default priority. The default ordering of these modules is important to ensure they work correctly. |
|
|
Древовидный вид