Hello!
There is a known issue caused by some obsolete client like old version
okhttp (incomplete protocol implements).
Here is the ticket: https://trac.nginx.org/nginx/ticket/1397.
___
nginx-devel mailing list
nginx-devel@nginx.org
Hello!
I think the handler return code is improper.
You might need to learn the function ngx_http_core_rewrite_phase
and decide a proper return code to this checker so that subsequent phases
handler will not
be invoked.Otherwise some content handlers can still can get involved.
(these content
Hello!
I am wondering some details about HTTP/2 Huffman.
There is a statement (
http://hg.nginx.org/nginx/file/tip/src/http/v2/ngx_http_v2_huff_encode.c#l238
)
buf |= (ngx_uint_t) –1 >> pending;
I am confused about this statement, why should we set the low bits of but
to 1 (sizeof(buf) -
# HG changeset patch
# User Alex Zhang
# Date 1520229178 -28800
# Mon Mar 05 13:52:58 2018 +0800
# Node ID 03ecef37a93d541e55802393636c101a4da14550
# Parent 265c29b0b8b8c54b1c623268481ed85324ce3c79
HTTP/2: used bitwise operation to replace division and modulo.
# HG changeset patch
# User Alex Zhang
# Date 1516079440 -28800
# Tue Jan 16 13:10:40 2018 +0800
# Node ID 9ca5af970d2296a02acefb3070237c5f52119708
# Parent 93abb5a855d6534f0356882f45be49f8c6a95a8b
yield 499 while reading client body and client prematurely closed