Well to be fair, that is not the same as "you can not upload gzip'd content".
Your complaint seems to be "S3 doesn't automatically gunzip gzip files that I upload", which sounds like the desired behaviour to me. i.e. if I ever upload gzipped content to S3, it is because I want it to be served compressed over HTTP, or because I am moving a compressed backup file to S3. In neither case would gunzipping be desirable, although I do appreciate that compressing during the transfer, and decompressing on the other end, could save some bytes during transfers.
> Yes, the other things I could have meant would have been odd, so I'm not sure why you spent time typing them out.
It seemed clear that you were either confused about what features were supported by S3, or not expressing your complaint correctly. The reason behind typing them out was trying to politely point this out, while describing some of the real-world use cases for using gzip'd files in S3 (partially to highlight why it would not make sense for S3 to gunzip files automatically).
I felt this would be a more useful comment than "you are wrong, you can upload gzip'd files to S3", or just downvoting your comment for being incorrect.
Your complaint seems to be "S3 doesn't automatically gunzip gzip files that I upload", which sounds like the desired behaviour to me. i.e. if I ever upload gzipped content to S3, it is because I want it to be served compressed over HTTP, or because I am moving a compressed backup file to S3. In neither case would gunzipping be desirable, although I do appreciate that compressing during the transfer, and decompressing on the other end, could save some bytes during transfers.