This property specifies whether output from an ASP application will be buffered. If the value is TRUE (default), all output from the application is collected in the buffer before the buffer is flushed to the client browser. If this property is set to FALSE, output from ASP scripts will be written to client browser as it becomes available.
With buffering on, the ASP application will have to completely process the ASP script before any output is received by the client browser. For this reason, applications for which buffering has been turned on could seem slower to users than those applications for which buffering is turned off, even though the total time taken for the buffered script is less. Therefore, if buffering is turned on, you should consider using the Response.Flush method to pass the user pieces of content as the script is being processed.
Note If buffering is turned off, any methods that modify existing HTTP headers, or generate new headers, must be executed before the content body is sent to the client browser. If buffering is turned on, this restriction is unnecessary.
Important If you installed IIS 5.0 by upgrading from a previous version of IIS, the default setting for this property will be FALSE, not TRUE.
Data type | Boolean |
Default value | TRUE |
Inheritance | Inheritable |
This property is accessible at the following locations:
Metabase Path | Key Type |
/LM/W3SVC | IIsWebService |
/LM/W3SVC/N | IIsWebServer |
/LM/W3SVC/N/ROOT | IIsWebVirtualDir |
/LM/W3SVC/N/ROOT/WebVirtualDir | IIsWebVirtualDir |
/LM/W3SVC/N/ROOT/WebVirtualDir/WebDirectory | IIsWebDirectory |
The following table lists additional information required only for code that uses the IIS Admin Base Object.
Metabase identifier | MD_ASP_BUFFERINGON |
Data type | DWORD_METADATA |
User type | ASP_MD_UT_APP |