Datasheet

Registry Setting Value Name Description

StopBinFiltering Set this value to 1 to stop the filter from blocking

requests to paths that include

/bin. This setting

will affect all ASP.NET 1.1 and 2.0 applications on

the server.

StopProtectedDirectoryFiltering Set this value to 1 to stop the filter from blocking

requests to reserved ASP.NET directories that

include a path starting with

/app_. Because this

setting is new to ASP.NET 2.0, it will only affect all

ASP.NET 2.0 applications on the server.

Setting either one of these Registry settings will affect

all

of your websites. There is no mechanism to

selectively turn off directory blocking for only specific applications or specific websites.

Dynamic versus Static Content

After a request has flowed through all of the ISAPI filters configured for a website, IIS decides whether

the requested resource is considered static content or dynamic content. This decision really depends on

whether a custom ISAPI extension has been configured and associated with the file extension of the

requested resource. For example, if you were to request

http://localhost/foo.htm, in the default

configuration of IIS, the

.htm extension is registered as a type of static content server directly by IIS.

The configuration of static versus dynamic content is determined by a combination of settings in IIS6:

❑ MIME type mappings

❑ File extension to ISAPI extension mappings

❑ The presence of wildcard application mappings (if any)

MIME Type Mappings

IIS6 is configured with several well known static file extensions in its list of Multipurpose Internet Mail

Extensions (MIME) type mappings. The reason that MIME type mappings are so important in IIS6 is that

without a MIME type mapping, an HTTP request for a file results in a 404 error, even if the file does exist

on the file system. For example, if a text file,

foo.xyz, exists at the root of a website, requesting

http://localhost/foo.xyz results in a 404.

However, the web server’s allowable MIME types can be edited to allow IIS6 to recognize

.xyz as a

valid file extension. In Figure 1-3, the IIS6 MMC is shown being used to register

.xyz as a valid file

extension.

Initial Phases of a Web Request

04_596985 ch01.qxp 12/14/05 7:46 PM Page 9