Configuring FileType filters

It is possible to configure the IBM® HTTP Server to increase performance of the IBM Docs editors. This might have been done when the IBM HTTP Server was configured with IBM Connections, but if not, complete the following steps.

Procedure

Configure FileType filters on the IBM HTTP Server:
  1. Log in to the Integrated Solutions Console.
  2. Navigate to Servers > Server Types > Web Servers.
  3. Click one of the web servers used by IBM Connections, such as IHS_SERVERNAME_1, for example, DocsLab01-IHS.
  4. Under Additional Properties, click Configuration file.
  5. Add the following lines to the end of the file:
    #Adding FileType Compression configuration
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule headers_module modules/mod_headers.so
    
    #Only the specified MIME types will be compressed.
    AddOutputFilterByType DEFLATE application/atom+xml 
    AddOutputFilterByType DEFLATE application/atomcat+xml 
    AddOutputFilterByType DEFLATE application/javascript 
    AddOutputFilterByType DEFLATE application/json 
    AddOutputFilterByType DEFLATE application/octet-stream 
    AddOutputFilterByType DEFLATE application/x-javascript 
    AddOutputFilterByType DEFLATE application/xhtml+xml 
    AddOutputFilterByType DEFLATE application/xml 
    AddOutputFilterByType DEFLATE text/css 
    AddOutputFilterByType DEFLATE text/html 
    AddOutputFilterByType DEFLATE text/javascript 
    AddOutputFilterByType DEFLATE text/plain 
    AddOutputFilterByType DEFLATE text/xml 
    AddOutputFilterByType DEFLATE text/xsl
    
    # Ensures that images and executable binaries are not compressed 
    SetEnvIfNoCase Request_URI \\.(?:gif|jpeg|png|exe)$ no-gzip dont-vary
    
    # Ensure that proxies Do not deliver the wrong content
    Header append Vary User-Agent env=!dont-vary
  6. Click OK twice, and then click Save.
  7. Repeat for the remaining IBM HTTP servers.
  8. Perform a full resynchronization on all of the nodes.
    Note: You can verify in the httpd.conf that the correct path to the plugin-cfg.xml is entered for the WebSpherePluginConfig entry.