FogBugz 7 Online Help

Enabling HTTP Compression for Faster FogBugz Page Loads

HTTP compression can drastically improve FogBugz performance by reducing the amount of bandwidth consumed for each page load.  Enabling HTTP compression is easy for both IIS and Apache, and you'll find that your FogBugz pages are reduced to approximately 10% of their original size.  You will pay a slight penalty in increased server CPU load, but we think that the tradeoff makes HTTP compression a no-brainer.


Download the free tool available at (follow the links to download want to download  FlatCompression's extended documentation is available, but you should only need to follow the simple steps below.

  1. Unzip FlatComp-R-1.20.226.dll and place it in C:\Windows\system32\inetsrv
  2. Go to Control Panel | Administrative Tools | Internet Information Services
  3. Expand "Local Computer", right-click on "Web Sites", and click Properties
  4. Click the "ISAPI Filters" tab, click Add, and enter "FlatCompression" as the filter name.
  5. Browse to C:\Windows\system32\inetsrv\FlatComp-R-1.20.226.dll for the executable.
  6. Click Ok, restart IIS.

Note (IIS5 and IE6 only): if you enable IIS5 FlatCompression and use an old minor version of Internet Explorer 6, you may occassionally receive javascript errors due to a bug in this older IE.  Running Windows Update on the client machine or just getting a newer version of IE6 will resolve the issue (in particular, this bug has been confirmed on IE 6.0.2600.0000.xpclient.010817-1148 with no updates).

    IIS 6

    IIS 6 ships w/ support for HTTP compression, but you need to take a couple configuration steps.  Scott Forsyth's walkthrough is the best detailed explanation we've found.  Follow his three simple sections (Enable Compression in IIS, Create a Web Service Extension, and Now for the metabase changes), and you should be all set.

    IIS 7

    IIS 7 supports HTTP compression as well. For a complete instructions on how to configure it, view the Microsoft TechNet Article.


    That's it!  Your compression should be up and running, and if you keep an eye on your network traffic you'll notice that individual requests consume significantly less bandwidth.