On Tuesday 27 October 2015 22:47:56 Shengtuo Hu wrote:
> Hi Valentin,
>
> Do you mean that because NGINX is fast enough and the network environment
> is good, so NGINX can process only one request at every moment?
Exactly.
>
> My purpose is to figure out the priority mechanism. It seems only
>
Hi Valentin,
Do you mean that because NGINX is fast enough and the network environment
is good, so NGINX can process only one request at every moment?
My purpose is to figure out the priority mechanism. It seems only
when there is limited capacity for sending, priority will be used to
select stre
Hello Nginx users,
Now available: Nginx 1.9.6 for Windows http://tiny.cc/nginxwin196 (32-bit
and 64-bit versions)
As of version 1.9.6 (and future releases) many more modules are compiled in
by default, including HTTP2.
These versions are to support legacy users who are already using Cygwin
based
Changes with nginx 1.9.6 27 Oct 2015
*) Bugfix: a segmentation fault might occur in a worker process when
using HTTP/2.
Thanks to Piotr Sikora and Denis Andzakovic.
*) Bugfix: the $server_protocol variable was empty when using HTTP/2.
On Tuesday 27 October 2015 17:33:22 Shengtuo Hu wrote:
> Hi,
>
> I got some problems when testing priority feature in Nginx 1.9.5.
>
> Here is the detail about my test:
> https://gist.github.com/h1994st/f21cdb7125a65c8f7182
>
> Why are the response sequence from these two servers different?
>
>
Hi,
I got some problems when testing priority feature in Nginx 1.9.5.
Here is the detail about my test:
https://gist.github.com/h1994st/f21cdb7125a65c8f7182
Why are the response sequence from these two servers different?
The response sequence of nghttp server is my expected result.
Could you t
