Setting file system compression settings on the Web Site document

Use the settings in the File System Compression Settings section on the Configuration tab of the Web Site document to enable creating gzip (GNU zip) compressed files and to define the values for file system compression settings. When you use the settings on the Web site document, the settings apply to those Web sites to which the Web site document applies.


  1. From the Domino® Administrator, choose ConfigurationWebInternet Sites.
  2. Choose the Web Site document you want to edit and click Edit Document.
  3. Click Configuration. Under File System Compression Settings, complete these fields:
    Table 1. File System Compression Settings options



    Compressed files

    Choose Enable if you want the Domino® HTTP server to check for and serve gzip (GNU zip) compressed versions of static files and to activate other compression settings on this tab.

    Include MIME types

    Specify the types of MIME files that can be considered for compression. MIME types that are specified in the Exclude MIME type field will not be compressed even if they fit the parameters of MIME types to be included for compression.

    Exclude MIME types

    Specify the types of MIME files to be excluded from consideration for compression. File types specified here should be a subset of those types specified in the Include MIME types field.

    Create compressed files

    Choose Enable if you want the Domino® HTTP server to create gzip (GNU zip) compressed versions of static file system files. Compressed files are created when they do not exist or the uncompressed version of the file has a time-date stamp that is later than the compressed version of the file.

    Wait time out

    Specify a maximum wait time out. Allows you to change the timeout for a pending HTTP request that is waiting for compression to complete. The default setting is 500 milliseconds. If two or more HTTP clients request a file that needs to be compressed, the server compresses the file for one client. While that compression takes place, all other requests for that file wait for compression to complete. If the client wait time exceeds the timeout value, the original uncompressed file is delivered to the HTTP client. Compressing large files can create a server "bottle neck" when there are many requests for the same large file while the file is being compressed by the server. It is strongly recommended that very large files be compressed offline.

    Minimum file size

    Specify a minimum file size of files to be considered for compression. The default is 300 bytes. If a file is smaller than the minimum file size specified for a file, a compressed file is not created.

  4. Save and close the document.
  5. Restart the Web server so that the settings to take effect.