UltiDev Cassini和< system.webServer> web.config设置 [英] UltiDev Cassini and <system.webServer> web.config settings

问题描述

MS Cassini开发Web服务器是一个很好的产品，它以类似于IIS7的方式执行Web请求。每个请求（静态内容的事件）都通过相同的.Net管道，没有例外。所有自定义HttpModule都可以处理任何请求。

MS Cassini Development Web Server is a nice product that executes web requests in a similar way that IIS7 does. Every request (event for static content) goes through the same .Net pipeline without exception. All custom HttpModule can handle any request.

但有时你不希望这些模块对某些内容（通常是静态内容）执行。在这方面，MS Cassini不读/服从IIS7的< system.webServer> web.config设置。我对这些设置特别感兴趣。

But sometimes you don't want these modules to execute for certain content (most often static content). In this regard, MS Cassini doesn't read/obey <system.webServer> web.config settings like IIS7 does. I'm particularly interested in these settings.

<system.webServer>
    ...
    <handlers />
    <modules />
</syste.webServer>

UltiDev的Cassini （从MS Cassini升级的单独的可支付产品）Web服务器读取这些设置，并像web.config所指示的那样执行？ / p>

Does UltiDev's Cassini (a separate payable product upgraded from MS Cassini) web server read these settings and execute as the web.config tells it to?

推荐答案

Cassini的行为不像IIS7，而是像IIS6。所以你应该使用< system.web> 部分，而不是< system.webServer> ：

Cassini doesn't behave like IIS7, but like IIS6. So you should use <system.web> sections instead of <system.webServer>:

<system.web>
    ...
    <httpHandlers />
    <httpModules />
</system.web>

所有请求通过ASP.NET管道的原因是因为它是硬连线的在IIS6中具有通配符映射）

The reason all requests go through the ASP.NET pipeline is because it is hardwired to do that (like having wildcard mapping on in IIS6)

这篇关于UltiDev Cassini和< system.webServer> web.config设置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！