HTTP/2: improved handling of END_STREAM in a separate DATA frame.

The save body filter saves the request body to disk once the buffer is full.
Yet in HTTP/2 this might happen even if there is no need to save anything
to disk, notably when content length is known and the END_STREAM flag is
sent in a separate empty DATA frame.  Workaround is to provide additional
byte in the buffer, so saving the request body won't be triggered.

This fixes unexpected request body disk buffering in HTTP/2 observed after
the previous change when content length is known and the END_STREAM flag
is sent in a separate empty DATA frame.

diff --git a/src/http/v2/ngx_http_v2.c b/src/http/v2/ngx_http_v2.c
index 461bbff8405fc7e3af1d9182a18604d8b135e8df..a037e7a5205847adcb3db5c1b4184f9f39028a1e 100644 (file)
--- a/src/http/v2/ngx_http_v2.c
+++ b/src/http/v2/ngx_http_v2.c
@@ -4034,6 +4034,9 @@ ngx_http_v2_read_request_body(ngx_http_request_t *r)
 
     if (len < 0 || len > (off_t) clcf->client_body_buffer_size) {
         len = clcf->client_body_buffer_size;
+
+    } else {
+        len++;
     }
 
     if (r->request_body_no_buffering && !stream->in_closed) {