Fix Content-Length header when serving gzipped content

The refactor in a56003d8 to support the Range header broke compliance
with the HTTP spec. When we find a gzipped resource to serve up, ensure
we use the correct Content-Length of the compressed file, not the
original one.
Merge pull request #240 from toofishes/static-gz-length

Fix Content-Length header when serving gzipped content