Welcome! Log In Create A New Profile

Advanced

Re: No gzip compression for HTTP status code 202

Maxim Dounin
December 04, 2018 06:16AM
Hello!

On Tue, Dec 04, 2018 at 05:56:00AM -0500, hpuac wrote:

> I noticed that the ngx_http_gzip_module is not compressing the response body
> if the HTTP response status code is 202 (Accepted).
> After having a look at the code, it looks like the filter is only active if
> the status code is 200, 403 or 404.
> (
> https://trac.nginx.org/nginx/browser/nginx/src/http/modules/ngx_http_gzip_filter_module.c#L249
> )
> Is there any particular reason to not compress other status codes?
> And if not, could we adjust this logic to also compress others, for example
> everything except 204 (No Content)?

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

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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: 223
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