Gzip outgoing request body (POST|PATCH|PUT)?

[kjs3]

This issue shows how to compress request bodies but I'm wondering why that wouldn't be done automatically with the {gzip: true} option?

Is this just a technical issue that hasn't been implemented yet?

[tzachshabtay]

Joining this question. I think the "gzip" option relates to the response compression, not to the request compression. It sounds to me like there should be 2 options: "gzip_response" and "gzip_request".

There's an issue from 2012 (#234) which was closed, the comments implying that this is now supported? But it's not, right? This left me confused.

[kjs3]

@tzachshabtay: Yes, this confused me too.

You are correct. The gzip option only refers to decompressing the response. I had to manually gzip the outgoing POST body.

I'm not sure this module should implement outgoing compression though. I don't believe servers are typically setup to inflate/decompress incoming request bodies. I controlled the server side in my case so I manually decompressed on that end. Saving some bandwidth seemed worth it but it was definitely a custom thing.

If I'm wrong and request body compression is expected on the server then I would think this should be implemented.

[tzachshabtay]

What server software are you using? Using NodeJS + Express, and it seems that the server automatically decompressed my manual gzip compressed json body (had to put Content-Encoding=gzip on the request).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.