connect-gzip icon indicating copy to clipboard operation
connect-gzip copied to clipboard

Gzip middleware for node.js Connect and Express

Results 10 connect-gzip issues
Sort by recently updated
recently updated
newest added

Hello, I'm getting some an error when I try to run a gulp script with gulp-connect and connect-gzip. The problem is when I try to gzip an image file, the...

Original library doesn't seem to be maintained anymore, but here are my changes anyway as we use this fork in production. - internal zlib (from fork by @cweider) for dynamic...

Requires node ≥ 0.6.0 and breaks the API, but it stops shelling out.

`child_process.spawn` in Node.js versions prior to 0.7 use the `exit` event to signal that the child process has finished; newer versions use the `close` event. Listening to the `exit` event...

When quickly gzipping multiple files (multiple requests). Probably related to this: https://github.com/joyent/node/issues/4112 From that issue: "Not a bug. In 0.8 you'd want to listen for the "close" event. See the...

In connect 2.3.7 the `send` function was split into a separate module (senchalabs/connect@3ea7fa2f74930a7f924c4c8eba0a4c292090dd03), which breaks `connect-gzip`. This is unfortunate because `connect-gzip` specifies a very liberal version range in `package.json`, so...

The version in npm is 0.1.6, but it says 0.1.5 in `package.json` here on github. Forgot to push?

I was running connect-gzip from a directory that has a space in one of its parent dirs, and that makes the exec commands fail. The code should use an arguments...

Stumbled on this while looking into a reported [issue](https://github.com/bnoguchi/everyauth/issues/35) with `everyauth`. The problem is that the session is not properly persisted just before the redirect. To reproduce: 1. Use the...