With this middleware enabled, every HEAD request that matches the filters will cause the following warning to be printed: This type of response MUST NOT have a body. Ignoring write() calls. This checks that `req.method !== 'HEAD'` before compressing. This is a simple fix and matches the future compress middleware that is going to be included with connect.
…sible with Connect 1.4.0, which now won't overwrite the Content-Type header based on the file extension if Content-Type is already set.
…containing '..'). Also, add the appropriate Content-Type header before passing off to the static provider. Right now, the static provider will just overrite this, but once that is fixed, then it will be possible to name files with the more standard file.ext.gz instead of gz.file.ext format being used now.
… middleware now works with various ways of setting headers and writing to the response. Had to make a small change to expresso to support requests for binary files.
… version based on compress.js, since it mostly duplicated functionality.
…d making sure the request works correctly when the gzip file is not made.
… advantage of any features in that library, including 304 support and max-age.