Hi, Another error I met recently. It occurred when both padding and continuation are enabled. A normal HEADERS frame was divided as follows: HEADERS ===> HEADERS(PADDED_FLAG) + CONTINUATION + CONTINUATION After sending these frames, I got an error. In the debug log file, I found "client sent inappropriate frame while CONTINUATION was expected while processing HTTP/2 connection". Thby h1994st - Nginx Mailing List - English
Hi, I was using "nghttp" command line tool to test NGINX. I enabled "continuation" option in "nghttp" command line tool, which filled the HEADERS frame with a very large header field/value. Then I got an GOAWAY frame with error code of "ENHANCE_YOUR_CALM(0x0b)". Then I checked the debug log file of the server, and found "client exceeded http2_max_headeby h1994st - Nginx Mailing List - English
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 streams for transmitting frames. I misunderstood this part before. Your explanation is quite clear. I wiby h1994st - Nginx Mailing List - English