Specifies the number of times the process specified in processPath is allowed to crash per minute. If this limit is exceeded, the module stops launching the process for the remainder of the minute. Specifies the duration for which the ASP. In versions of the ASP. NET Core 2. Doesn't apply to in-process hosting. For in-process hosting, the module waits for the app to process the request.
Valid values for minutes and seconds segments of the string are in the range Use of 60 in the value for minutes or seconds results in a - Internal Server Error. Duration in seconds that the module waits for the executable to start a process listening on the port. If this time limit is exceeded, the module kills the process. When hosting in-process : The process is not restarted and does not use the rapidFailsPerMinute setting.
When hosting out-of-process : The module attempts to relaunch the process when it receives a new request and continues to attempt to restart the process on subsequent incoming requests unless the app fails to start rapidFailsPerMinute number of times in the last rolling minute.
If true, stdout and stderr for the process specified in processPath are redirected to the file specified in stdoutLogFile. Specifies the relative or absolute file path for which stdout and stderr from the process specified in processPath are logged.
Relative paths are relative to the root of the site. Any path starting with. Any folders provided in the path are created by the module when the log file is created.
Using underscore delimiters, a timestamp, process ID, and file extension. Environment variables can be specified for the process in the processPath attribute.
Environment variables set in this section take precedence over system environment variables. The following example sets two environment variables in web. A developer may temporarily set this value in the web. An alternative to setting the environment directly in web. This approach sets the environment in web. For example, IIS configuration is functional for dynamic compression. NET Core app. To set environment variables for individual apps running in isolated app pools supported for IIS Configuration sections of ASP.
Typically the collection directive names are "add", "remove" and "clear", but some collections use different names for clarity for example, the collection is using "site" instead of "add". This is done by specifying values for addElement, removeElement and clearElement in the collection schema. If a collection directive is missing from the schema, the collection will not support it.
The collection schema may specify the name of a default element that will be used as a container of default values for collection elements this complements isCollectionDefault in the element schema.
For example, the collection is using siteDefaults as the default element. For example, consider two levels of configuration: applicationHost. In applicationHost. This is mostly done to support legacy collections in the.
NET framework in machine. Some collections may allow additional attributes in them, beyond those specified in the schema. It is mostly done to support provider-based collections in the. NET framework. Every value must have a friendly name and a numerical value. Every attribute of type "flags" must define its flag values in a corresponding XML element in the schema.
Every flag must have a friendly name and a numerical value that can be ORed together with other values to form combinations; therefore, the value should be in multiples of 2. Attribute validation is done when parsing the XML to get a section from the file, and when calling the configuration API to set values. If validation fails, it fails the desired operation getting the section or setting the invalid value. Each attribute may associate one validator for its value.
This is done by specifying the appropriate validator name in the validationType, and additional parameters in the validationParameter in the attribute schema. Every configuration file is an XML file and may optionally include the following line as the first line:.
The rest of this document walks through the rest of the sections in the file. This is the very first section in the file. It contains a list of all other sections in the file. Note that other configuration files may have a section as well, at the very top of the file. This may be useful to register sections at levels lower than the global level.
These sections will be registered for that scope of the namespace only. The sections are structured by their hierarchy of containing section groups. Add a comment. Active Oldest Votes. Improve this answer. Rudy Rudy 2 2 silver badges 7 7 bronze badges. Was it possible to edit this before IIS7? This was introduced beginning with IIS 7. IIS 5 and earlier used a binary metabase format. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.
0コメント