IIS keeps trying to manage URL requests, are there modules or filters that need to be disabled?

Everything I’ve read says to handle the 404 error by using the urlRewrite. I tried that, but IIS does not seem to allow that module to handle the request. I turned off all the modules and filters, and now I just get the IIS “not found” message.

I have a trace log, but that thing is hundreds of pages of XML. Is there anything I should be looking for, in terms of what kind of processing IIS is doing that it should not be?

Here is my web.config –

<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name=”Main Rule” stopProcessing=”true”>
<match url=”*” />
<conditions logicalGrouping=”MatchAll”>
<add input=”{REQUEST_FILENAME}” matchType=”IsFile” negate=”true” />
<add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” negate=”true” />
</conditions>
<action type=”Rewrite” url=”index.php” />
</rule>
</rules>
</rewrite>
<httpErrors existingResponse=”PassThrough” />

<modules>
<remove name=”IsapiModule” />
<remove name=”IsapiFilterModule” />
</modules>
<handlers>
<remove name=”OPTIONSVerbHandler” />
<remove name=”TRACEVerbHandler” />
<remove name=”ExtensionlessUrlHandler-Integrated-4.0″ />
<remove name=”ExtensionlessUrlHandler-ISAPI-4.0_64bit” />
<remove name=”ExtensionlessUrlHandler-ISAPI-4.0_32bit” />
<remove name=”StaticFile” />

</handlers>
<isapiFilters>
<remove name=”ASP.Net_4.0_32bit” />
<remove name=”ASP.Net_4.0_64bit” />
<remove name=”UrlScan 3.1″ />
</isapiFilters>
</system.webServer>
<system.web>
<customErrors mode=”Off”>
</customErrors>
</system.web>
</configuration>

Is IIS just unsuitable for running WordPress? It seems like other people are able to do it, I’m wondering why we’re having issues.

Read more here:: IIS keeps trying to manage URL requests, are there modules or filters that need to be disabled?

Leave a Reply

Your email address will not be published. Required fields are marked *