Welcome! Log In Create A New Profile

Advanced

Re: No gzip compression for HTTP status code 202

December 04, 2018 07:09AM
Hey!

> http://mailman.nginx.org/pipermail/nginx/2012-September/035338.html

Thank you for the quick answer!
Would it make sense to add that information to the documentation?
https://nginx.org/en/docs/http/ngx_http_gzip_module.html

You named some examples why not to compress 206, 304, 400, 500, but is there any particular reason to not compress 202?
Status codes like 201 and 202 should like 200 be common and safe response codes that could be compressed.
I had a quick look and for example undertow is also compressing 202 responses.
What do you think about making the status codes that will get compressed configurable?

Best regards,
Hans
Subject Author Posted

No gzip compression for HTTP status code 202

hpuac December 04, 2018 05:56AM

Re: No gzip compression for HTTP status code 202

Maxim Dounin December 04, 2018 06:16AM

Re: No gzip compression for HTTP status code 202

hpuac December 04, 2018 07:09AM

Re: No gzip compression for HTTP status code 202

Maxim Dounin December 04, 2018 07:40AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 320
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready