Meaning

by

Modules Preconditions:

The IIS core engine uses preconditions to determine when to enable a particular module. Performance reasons, for example, might determine that you only want to execute managed modules for requests that also go to a managed handler. The precondition in the following example (precondition="managedHandler") only enables the forms authentication module for requests that are also handled by a managed handler, such as requests to .aspx or .asmx files:

<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" preCondition="managedHandler" />

If you remove the attribute precondition="managedHandler", Forms Authentication also applies to content that is not served by managed handlers, such as .html, .jpg, .doc, but also for classic ASP (.asp) or PHP (.php) extensions. See “How to Take Advantage of IIS Integrated Pipeline” for an example of enabling ASP.NET modules to run for all content.

You can also use a shortcut to enable all managed (ASP.NET) modules to run for all requests in your application, regardless of the “managedHandler” precondition.

To enable all managed modules to run for all requests without configuring each module entry to remove the “managedHandler” precondition, use the runAllManagedModulesForAllRequests property in the <modules> section:

<modules runAllManagedModulesForAllRequests="true" />

When you use this property, the “managedHandler” precondition has no effect and all managed modules run for all requests.

Copied from IIS Modules Overview: Preconditions

More Related Contents:

  1. Using different Web.config in development and production environment
  2. How do you modify the web.config appSettings at runtime?
  3. Access-control-allow-origin with multiple domains
  4. Forms authentication timeout vs sessionState timeout
  5. Avoid web.config inheritance in child web application using inheritInChildApplications
  6. Which gets priority, maxRequestLength or maxAllowedContentLength?
  7. Setting up connection string in ASP.NET to SQL SERVER
  8. Use Visual Studio web.config transform for debugging [duplicate]
  9. How to set the Default Page in ASP.NET?
  10. ASP.NET web.config: configSource vs. file attributes
  11. Difference between and ?
  12. Reading web.config from JavaScript
  13. Web Application Problems (web.config errors) HTTP 500.19 with IIS7.5 and ASP.NET v2
  14. Setting up redirect in web.config file
  15. HTTP Error 500.19 – Internal Server Error
  16. Escape quote in web.config connection string
  17. How to configure invariant culture in ASP.NET globalization?
  18. What are the Web.Debug.config and Web.Release.Config files for?
  19. Login failed for user ‘NT AUTHORITY\NETWORK SERVICE’
  20. Nested ASP.NET ‘application’ within IIS inheriting parent config values?
  21. Store String Array In appSettings?
  22. How to encrypt one entry in web.config
  23. Web Config Transform not working
  24. Is it possible to configure a location in Web.config to only allow local connections
  25. Programmatically register HttpModules at runtime
  26. The configuration section ‘system.web.extensions’ cannot be read because it is missing a section declaration
  27. web.config and app.config confusion
  28. Unrecognized attribute ‘targetFramework’. Note that attribute names are case-sensitive
  29. Specify more than one directory in Web.Config’s Location Path element
  30. URL Routing, Image Handler & “A potentially dangerous Request.Path value”

Leave a Comment