Hi,
Could anybody tell me the http 2 status, and what's level of support by
nginx?
Thanks so much!
B.R.
___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
details: http://hg.nginx.org/nginx/rev/82b0cd4a0324
branches:
changeset: 6616:82b0cd4a0324
user: Ruslan Ermilov
date: Wed Jul 06 13:10:06 2016 +0300
description:
Version bump.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 lines):
details: http://hg.nginx.org/nginx/rev/8bf484eef9ab
branches:
changeset: 6617:8bf484eef9ab
user: Ruslan Ermilov
date: Wed Jul 06 13:22:29 2016 +0300
description:
Use NGX_MAX_PATH_LEVEL where appropriate.
The macro was unused since 0.7.44.
diffstat:
src/core/ngx_file.c
Hey Maxim,
> I'm not convinced this feature is needed at all. It looks more
> like a Google-specific experiment, and this is not something I
> would like to see in nginx code.
Wait, what? Are you talking about trailers as defined in RFC7230 (and
previously in RFC2616 from 1999, when Google barel
Hi,
It seems the global variable 'ngx_http_headers_out' in
src/http/ngx_http_header_filter_module.c isn't used at any where.
B.R.
___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
On Thu, Jul 07, 2016 at 10:25:44AM +0800, 洪志道 wrote:
> Hi,
>
> It seems the global variable 'ngx_http_headers_out' in
> src/http/ngx_http_header_filter_module.c isn't used at any where.
>
> B.R.
Yes.
___
nginx-devel mailing list
nginx-devel@nginx.org
