Isapimodule or cgimodule must be in the module list

http://blog.csdn.net/jiangxuchen/article/details/8758847

The default in IIS7 is that script map processing has been loaded. But today, a WIN7, installed IIS, but found no. Then manually go to the installation, when adding HTML mapping prompts: The module list must have Isapimodule or Cgimodule

Google has not found the reason for half a day. The answer was found later. Method is simple, open or close Windows features (these steps can be simplified to win+r run optionalfeatures), Internet Information Services--World Wide Web services--in the control Panel, programs and features Hair function, put all of the following on the hook! Reboot, Success!

Issue two: The page you requested cannot be provided because of the ISAPI and CGI Restrictions list settings on the WEB server. IIS root node (first node), right "ISAPI and CGI restrictions", set the Forbidden Dotnet version entry to allow.

The Web. config must be IIS7 under the following paragraph:

==========================================

<system.webServer>         <modules>              <add name= "All" type= "Urlrewriter.modulerewriter" precondition= " Managedhandler "/>         </modules>         

HTTP error 404.0-not found the resource you are looking for has been deleted, renamed, or temporarily unavailable.

ASP. NET config pseudo-static rules

First step : Download the urlrewriter component from any of the following addresses:

1:http://download.csdn.net/source/524514

The same project, another site (the same physical path), results in the next 404.0 error, the original is Vista under application pool default 32 application properties impact, reference, set to True

2:http://www.nmju.net/UserFiles/URLRewriter.rar 3:http://download.microsoft.com/download/0/4/6/ 0463611e-a3f9-490d-a08c-877a83b797cf/msdnurlrewriting.msi

Step Two: Add a reference to the Urlrewriter assembly in your Web site project .

Step Three: Configure the webconfig file:

1. Join the <configSections> and </configSections> node header as follows:

<section name= "Rewriterconfig" requirepermission= "false" type= " URLRewriter.Config.RewriterConfigSerializerSectionHandler, urlrewriter "/>

2. join between <add verb= "*" path= "*.aspx" type= " Urlrewriter.rewriterfactoryhandler, Urlrewriter "/> <add verb=" * "path=" *.html "type=" Urlrewriter.rewriterfactoryhandler, Urlrewriter "/>

3. join between

<add type= "Urlrewriter.modulerewriter, Urlrewriter" name= "Modulerewriter"/>

4.Configure pseudo-static syntax: add <rewriterconfig></between <configuration> and </configuration> The rewriterconfig> node. Add pseudo-static rules between <RewriterConfig> and </RewriterConfig>:

< Rules>       <!--define pseudo-static the first rule begins < Span style= "FONT-SIZE:12PX;" >-->       <RewriterRule>         <lookfor >~/xxxx/view (. [ /d]*)/.html</lookfor>         <sendto>~/xxxx/view.aspx?id=$1</ Sendto>       </rewriterrule>

<!--define pseudo-static the first rule ends-- <!--define pseudo-static second rule start-- <RewriterRule> <lookfor>~/yy yy/(. [ /d]*)/view.html</lookfor> <SendTo>~/yyyy/view.aspx?id=$1</SendTo> </rewriterrule>

<!--define pseudo-static third rule end and so on.

</Rules>

Fourth : Configuration of IIS7.5 or IIS7.0

  1, Create a new application pool: Name: Any :webapp; select net Framework version (if your site 2.0, my is 4.0) in this I choose net Framwork v 4.030319. Managed pipeline mode is first temporarily set to Integrated mode. When the following settings are complete, set the managed pipeline mode to Classic mode. If the following settings do not set the application to Classic mode, pseudo-static functionality can be implemented, but the page style picture does not display properly this is the key to the setting.

2. Create a new Web site website to set the application program pool for this site to WebApp.

3, check your site such as website, and switch to the function view. Double-click handler mappings to do the following in the action section on the right side of the open window.

       3.1 "Add script map" -path is :*. html. executable file: c:/windows/microsoft.net/framework /v4.0.30319/aspnet_isapi.dll Note: If your site is 2.0. The executable file is: c:/windows/microsoft.net/framework/v2.0.50727/aspnet_isapi.dll. Name: Any, for example: html.       3.2, the "Add wildcard script map" request path is *. Executable file and 3.1 the same, name any all.

3.3, "managed handler Mappings"(path:* executable file:System.Web.UI.PageHandlerFactory name arbitrary such as html-integrate)

3.4, double-click website site to switch to the site features view. Then double-click the module, open the window, and then, under the Action section on the right, click Add Managed Module-Name: Any type:urlrewriter.modulerewriter and The application or managed handler makes a request call "on the previous option tick." (Remember to make sure to tick).

3.5, last step: Double-click the application pool for iis7.0 or 7.5. Locate the "WebApp" application pool in the application pool list. Double-click after opening. set the managed pipeline mode for the WebApp application pool to Classic mode.

It is noteworthy that in the third part of the 2, 3 points can be selected according to the needs of the program design, in some uncertain circumstances, may cause the application to appear abnormal.

Of course, there are simpler ways to configure iis7.0 and iis7.5. Install the official Microsoft URL package to the server, import the configuration rules file on the server,

Maxmatchcount 10

Rewriterule ^news/([0-9]+)/.html$ news/xx.aspx?id=$1 #注释

。。。。。

。。。。

notparsed Foo Bar

The file name suffix is. htaccess, the site is paused, click Urlwriter, Import Rules application can, of course, in the development process, in order to facilitate testing, it is best to combine the two methods, Then rewrite the relevant urlwriter in Web. config to comment or delete the configuration item!

Isapimodule or cgimodule must be in the module list