The Web.CONFIG files normally contain
managed settings, while the ApplicationHost.CONFIG file contains native code settings of
various sorts. For example, when you use basic or digest authentication, the settings appear in the
ApplicationHost.CONFIG file, rather than the Web.CONFIG file, as shown in Figure 25.2.
578 CHAPTER 25 MANAGING IIS
Figure 25.2
The ApplicationHost
.CONFIG file normally
contains native code
settings.
Even though the file appears quite complex, you can break the ApplicationHost.CONFIG file
into five major areas. Once you know which area to view for a particular kind of data, working with
the file becomes considerably easier. The following list describes each of the major areas.
configSections The configSections element defines the sections within the configuration
file. You??™ll never need to change anything in this element because IIS depends on a specific configuration
to accomplish tasks and you??™ll use other means to configure custom applications.
configProtectedData The configProtectedData element contains the security provider
information for the system. You normally won??™t need to change this information unless you
obtain a third-party provider (there aren??™t any available for IIS 7 at the time of this writing).
Pages:
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325