How does httpZip determine what files to safely compress?
There are all sorts of references out there to “smart compression” technologies — our process is very simple and logical. httpZip will only compress what can or should be compressed based on series of tests: • httpZip scans for the Accept-Encoding header in the user’s request (its value must be either GZip or Deflate or both). If present, the process continues. • Top-level MIME type of the would-be response is checked. Is this a top-level MIME type that httpZip is configured to compress? If so, the process continues. • The browser list for the requesting User Agent is reviewed. If there is a match, httpZip checks to see if the browser is listed as being able to handle the would-be request’s top-level MIME type. If yes, the process continues. • The previous two steps are repeated for the MIME sub-type. • If all of these checks have been passed, and there are no exclusions for the request, then httpZip will compress the Web server’s response. The compression settings for top-level and s
