Http2 Priority

[Valentin V. Bartenev]

On Monday 12 October 2015 23:16:39 Muhui Jiang wrote:
> Hi,
> 
> Valentin, thanks for your response.
> I rebuild the nginx --with-debug. And when I send request with my Jetty
> client code. Nothing is added to the error.log. And I am going to tell you
> the problem in detail.
> 
> First, my nginx configure below:
> 
> events {
> 
>     worker_connections  1024;
> 
> }
> 
> 

The error_log with debug must be configured here on the main level,
instead of being set in the specific server block.


[..]
> And the way my client send request is when client find A has been sent then
> send B,C,D. set the B,C,D depend on A.
> 
> A: img/clink/clinklittle128.png
> 
> B: js/preloadjs.min.js
> 
> C: index.html
> 
> D: css/infocard.css
> 
> A is a very large file.
> 
> Then the console of my java program:
[..]

>From this console output it is not clear what frames the client send
to nginx, especially when and on what value window updates are happened.


> 
> HeadersFrame at 6b3c76a4#1{end=false}img/clink/clinklittle128.png
> 
> DataFrame at 3ed90f5#1{length:8033,end=false}img/clink/clinklittle128.png
> 
> DataFrame at 3a83903a#1{length:159,end=false}img/clink/clinklittle128.png
> 
> DataFrame at 7f6d0358#1{length:8024,end=false}img/clink/clinklittle128.png
> 
> DataFrame at 776cc347#1{length:168,end=false}img/clink/clinklittle128.png

> DataFrame at 18e99f67#1{length:8015,end=false}img/clink/clinklittle128.png
> 
> DataFrame at 3ecdce00#1{length:177,end=false}img/clink/clinklittle128.png
> 
> DataFrame at 292d6d42#1{length:8006,end=false}img/clink/clinklittle128.png
> 

Such frame sizes probably are the result of limiting on flow control windows,
NGINX tries to create data frame as big as the windows allow.

  wbr, Valentin V. Bartenev