System.Web
2.0.0.0
System.Configuration.ConfigurationSection
The allows you to handle those parameters that affect the behavior of the ASP.NET runtime.
It refers to the node in the configuration file that is indicated by the <httpRuntime> element and can be used at any level in the configuration hierarchy.
The section contains directives that manage the following:
-
Request execution timeouts.
-
Directives to thread scheduling at the application level.
-
Directives that govern application queue limits.
-
Request length.
When running more than one application in a single process, you should lock down this section so that applications cannot elevate their relative priority to one another.
Configures the ASP.NET HTTP runtime. This class cannot be inherited.
Constructor
To be added.
Initializes a new instance of the class using default settings.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("apartmentThreading", DefaultValue="False")
System.Boolean
To be added.
The default value is false.
Gets or sets a value that indicates whether application apartment threading is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("appRequestQueueLimit", DefaultValue="5000")
System.Configuration.IntegerValidator(MinValue=1, MaxValue=2147483647)
System.Int32
To be added.
ASP.NET queues requests when there are not enough free threads to process them.
When the number of requests queued exceeds the limit imposed by this setting, incoming requests will be rejected with a "503 - Server Too Busy" error.
Gets or sets a value that indicates the maximum number of requests that ASP.NET queues for the application.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("delayNotificationTimeout", DefaultValue="00:00:05")
System.ComponentModel.TypeConverter(typeof(System.Configuration.TimeSpanSecondsConverter))
System.TimeSpan
To be added.
You can address the problem caused by some antivirus applications, when writing information back to the scanned files, by setting the property.
The problem occurs because file changes caused by antivirus scanning cannot be distinguished from the ones made by the user. The end result is the restart of the application whose files are being scanned.
Gets or sets the change notification delay.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enable", DefaultValue="True")
System.Boolean
To be added.
This setting affects the application domain or domains at the current node level and below.
Gets or sets a value that indicates whether the application domain is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableHeaderChecking", DefaultValue="True")
System.Boolean
To be added.
The purpose of this property is to enable encoding of the carriage return and newline characters, \r and \n, that are found in response headers.
In outbound response headers, the characters that are represented by the codes 0x1F and below are encoded and also the character 0x7F (delete character). The only exception is that the character 0x09 (the tab character) is unmodified.
This encoding can help to avoid injection attacks that exploit an application that echoes untrusted data contained by the header.
This property does not apply to the status line itself (status code and status description), but should apply to other headers. Although <httpRuntime> can be set at any level, this property is only applicable at the machine and application level.
When this property is true, which is the default, the \r or \n characters found in a response header are encoded to %0d and %0a. This defeats header-injection attacks by making the injected material part of the same header line. This might break the response but should not open attack vectors against the client. Echoing back untrusted data is never a good idea in any situation, though.
HTTP header continuations rely on headers spanning multiple lines and require new lines in them. If you need to use header continuations, you need to set the property to false. Because there is a performance impact from looking at headers, if you are certain you are already doing the right checks, turning off this feature can improve the performance of your application. Before you disable this feature, be sure you are already taking the right precautions in this area.
Gets or sets a value that indicates whether the header checking is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableKernelOutputCache", DefaultValue="True")
System.Boolean
To be added.
In order to cache a response, the following criteria need to be met:
-
Caching must be explicitly enabled by a page directive or by the caching API.
-
Caching must have an expiration policy so that the kernel knows when to discard it.
-
Caching cannot have any variable headers or parameters.
-
The request must not require any authentication.
This property is relevant only when Internet Information Services (IIS) version 6.0 or later is installed.
Gets or sets a value that indicates whether output caching is enabled.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("enableVersionHeader", DefaultValue="True")
System.Boolean
To be added.
This attribute is used by Visual Studio to determine which version of ASP.NET is in use. It is not necessary for production sites and can be disabled.
Gets or sets a value that indicates whether ASP.NET should output a version header.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("executionTimeout", DefaultValue="00:01:50")
System.Configuration.TimeSpanValidator(MinValueString="00:00:00")
System.ComponentModel.TypeConverter(typeof(System.Configuration.TimeSpanSecondsConverter))
System.TimeSpan
To be added.
The property indicates the maximum number of seconds a request is allowed to execute before being automatically shut down by ASP.NET. The default is 110 seconds. This time-out applies only if the debug attribute in the <compilation> element is set to false.
If the time-out expires an exception is raised. You can record the related information in the Application folder of the Event Log. You do this by enabling the application health monitoring in the <healthMonitoring> configuration element.
Gets or sets the allowed execution time for the request.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("maxRequestLength", DefaultValue="4096")
System.Configuration.IntegerValidator(MinValue=0, MaxValue=2147483647)
System.Int32
To be added.
The property specifies the limit for the buffering threshold of the input stream. For example, this limit can be used to prevent denial of service attacks that are caused by users who post large files to the server.
The value assigned to this property should be greater or equal to value assigned to the property.
Gets or sets the maximum request size.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("maxWaitChangeNotification", DefaultValue="0")
System.Configuration.IntegerValidator(MinValue=0, MaxValue=2147483647)
System.Int32
To be added.
A suggested value for the property would exceed the length of time to complete a copy during the deployment process.
The content might appear cached if you view it immediately after a copy-and-deploy process. This is typical behavior. The changes take effect when the wait period that you specified has elapsed.
Gets or sets the time interval between the first change notification and the time at which the application domain is restarted.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("minFreeThreads", DefaultValue="8")
System.Configuration.IntegerValidator(MinValue=0, MaxValue=2147483647)
System.Int32
To be added.
The property defines the minimum number of free threads to execute a request. If a sufficient number of threads are not available, the request will remain queued and periodic checks for thread availability will continue until the required amount of threads are present. The default value is 8.
ASP.NET keeps this many threads free for requests that require additional threads to complete their processing.
Gets or sets the minimum number of threads that must be free before a request for resources in this configuration scope can be serviced.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("minLocalRequestFreeThreads", DefaultValue="4")
System.Configuration.IntegerValidator(MinValue=0, MaxValue=2147483647)
System.Int32
To be added.
The property defines the number of free threads that ASP.NET keeps available to allow execution of new local requests. The intent is to avoid a possible deadlock with recursive reentry into the Web server.
Gets or sets the minimum number of free threads required to service a local request.
2.0.0.0
Property
System.Configuration.ConfigurationPropertyCollection
To be added.
To be added.
To be added.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("requestLengthDiskThreshold", DefaultValue="80")
System.Configuration.IntegerValidator(MinValue=1, MaxValue=2147483647)
System.Int32
To be added.
The property specifies the input-stream buffering threshold limit in number of bytes. Its value should not exceed the property value. After a request entity exceeds this threshold, it is buffered transparently onto disk.
Gets or sets the input-stream buffering threshold.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("requireRootedSaveAsPath", DefaultValue="True")
System.Boolean
To be added.
The property specifies whether the file name argument to SaveAs methods must be a rooted path. The ASP.NET process must have permission to create files in the specified location.
For more information, see the save methods defined in the class.
Gets or sets a value that indicates whether the file name must be a fully qualified physical file path.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("sendCacheControlHeader", DefaultValue="True")
System.Boolean
To be added.
The class checks both the property and the property to determine whether to send the cache-control:private header in the HTTP response. If either property is set to false, the header will not be sent. When the cache-control header is set to private, then the client will not cache the response in a shared cache.
Support for the property in the class is provided for compatibility with legacy applications; this property is obsolete in the .NET Framework version 2.0. For more information, see the class.
Gets or sets a value that indicates whether the cache-control:private header is sent as part of the HTTP response.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("shutdownTimeout", DefaultValue="00:01:30")
System.ComponentModel.TypeConverter(typeof(System.Configuration.TimeSpanSecondsConverter))
System.TimeSpan
To be added.
The property indicates the amount of time before an application is shut down gracefully. The default is 90 seconds.
Gets or sets the length of time the application is allowed to idle before it is terminated.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("useFullyQualifiedRedirectUrl", DefaultValue="False")
System.Boolean
To be added.
The property indicates whether client-side redirects are fully qualified (in the form http://server/path) or whether relative redirects are instead sent to the client.
Some browsers might have problems loading pages in cookieless sessions when this value is false.
Gets or sets a value that indicates whether the client-side redirects are fully qualified.
2.0.0.0
Property
System.Configuration.ConfigurationProperty("waitChangeNotification", DefaultValue="0")
System.Configuration.IntegerValidator(MinValue=0, MaxValue=2147483647)
System.Int32
To be added.
A suggested value for would exceed the length of time to complete a copy during the deployment process.
The content might appear cached if you view it immediately after a copy and deploy process. This is typical behavior. The changes take effect when the wait period that you specified has elapsed.
Gets or sets the waiting time before the next change notification.
2.0.0.0