integrated-pipeline-mode

问题 I have a large corp. web site with mixed classic asp and asp.net currently hosted with a Win 2003 server, IIS 6. I need to modify all the pages output with some html modifications regardless the world they comes from. The asp part it's really old and badly structured, thus I can't act on any kind of "general include" to apply all the changes we need. Lastly some asp pages outputs code from multiple OCX/COM objects... We are already planning a whole rewrite/migration to .net, but unfortunately

问题 I was deploying an ASP.NET MVC application last night, and found out that it is less work to deploy with IIS7 set to integrated mode. My question is what is the difference? And what are the implications of using one or the other? 回答1: Classic mode (the only mode in IIS6 and below) is a mode where IIS only works with ISAPI extensions and ISAPI filters directly. In fact, in this mode, ASP.NET is just an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). IIS just treats

问题 I am experimenting with the integrated authentication mode for static content in IIS7. I followed the instructions in this article: http://aspnet.4guysfromrolla.com/articles/122408-1.aspx It is working fine if I allow/deny access by login status (like in the article). However I want to allow/deny access based on roles (using the ASP.NET built in Roles Provider). When I put an allow rule for the role "Admin" in the web.config and deny rule for all other users I am not able to access the static

问题 I'm working on a website with legacy Classic ASP pages (being converted to ASP.NET on an as needed basis) and new ASP.NET pages. Use of IIS 7 Integrated Pipeline has been very helpful with our configuration. For example, we were able to get forms authentication working auto-magically with the classic ASP pages simply by configuring the appropriate sections of the web.config file (i.e. no changes were required to the Classic ASP pages, for more info see this). A colleague of mine believes that

问题 Firstly there's a great overview of the IIS7 HTTP request lifecycle and various settings that affect performance here: ASP.NET Thread Usage on IIS 7.0 and 6.0 Very specifically though, in dotNet 4 the defaults for maxConcurrentRequestsPerCPU and requestsQueueLimit are set to 5000. E.g. equivalent to: (in aspnet.config): <system.web> <applicationPool maxConcurrentRequestsPerCPU="5000" maxConcurrentThreadsPerCPU="0" requestQueueLimit="5000" /> (** see note below) </system.web> Seems to me that

问题 So IIS7 in Integrated Pipeline mode uses a IsapiFilterModule to shim ISAPI filter DLL's and fire off the correct "events" on the filters, which is quite different than previous versions of IIS or IIS7 in classic mode because this means that HttpModules fire off right along side ISAPI filters in Integrated Pipeline mode. So does anyone happen to know how ISAPI events (http://msdn.microsoft.com/en-us/library/ms524855.aspx) and the HttpModule events (http://msdn.microsoft.com/en-us/library

问题 With integrated pipeline, all requests are passed through ASP.NET, including images, CSS. Whereas, in classic pipeline, only requests for ASPX pages are by default passed through ASP.NET. Could integrated pipeline negatively affect thread usage? Suppose I request 500 MB binary file from an IIS server: With integrated pipeline, an ASP.NET worker thread would be used for the binary download (right?). With classic pipeline, the request is served directly by IIS, so no ASP.NET thread is used. To

问题 I tracked down what appears to be a defect causing a NullReferenceException in my ASP.NET MVC app. Did I break this, or should this break DotNetOpenAuth for the majority of installations? I get this: [NullReferenceException: Object reference not set to an instance of an object.] DotNetOpenAuth.AspNet.OpenAuthSecurityManager.GetUsername(HttpContextBase context) +27 DotNetOpenAuth.AspNet.OpenAuthSecurityManager.RequestAuthentication(String returnUrl) +341 Controllers.LoginController.Index()

问题 So I'm trying to iterate over Response.Headers for a custom caching job, but I'm getting the following error when I touch the thing: This operation requires IIS integrated pipeline mode It this possible to do in IIS6? Is there a workaround? var allHeaders = HttpContext.Current.Response.Headers; // error thrown as soon as it's accessed 回答1: AFAIK you cannot access the HTTP response headers unless you are running in integrated mode because they are sent by the server at a later stage of the

问题 I'm having troubles with a custom Error handler I built. It should be a HttpModule , but when I add it to my web.config 's system.webServer/modules tag, it is not initiated. This is my web.config section: <system.webServer> <modules> <add name="AspExceptionHandler" type="Company.Exceptions.AspExceptionHandler, Company.Exceptions" preCondition="managedHandler" /> </modules> </system.webServer> This is the code in my HttpModule : using System; using System.Web; using Company.Settings; using