nginx.git/src/http/v2, branch release-1.13.1

Introduced ngx_tcp_nodelay().

2017-05-26T19:52:48+00:00

HTTP/2: fixed segfault when memory allocation failed.

2017-05-23T17:19:39+00:00

If allocation of cleanup handler in the HTTP/2 header filter failed, then
a stream might be freed with a HEADERS frame left in the output queue.

Now the HEADERS frame is accounted in the queue before trying to allocate
the cleanup handler.

HTTP/2: reduced difference to HTTP/1.x in reading request body.

2017-04-24T11:17:13+00:00

Particularly, this eliminates difference in behavior for requests without body
and deduplicates code.

Prodded by Piotr Sikora.

HTTP/2: rejecting zero WINDOW_UPDATE with PROTOCOL_ERROR.

2017-04-24T11:16:57+00:00

It's required by RFC 7540.  While there is no real harm from such frames,
that should help to detect broken clients.

Based on a patch by Piotr Sikora.

HTTP/2: style and typos.

2017-03-26T08:25:01+00:00

Signed-off-by: Piotr Sikora

HTTP/2: fixed connection finalization.

2017-03-29T17:21:01+00:00

All streams in connection must be finalized before the connection
itself can be finalized and all related memory is freed.  That's
not always possible on the current event loop iteration.

Thus when the last stream is finalized, it sets the special read
event handler ngx_http_v2_handle_connection_handler() and posts
the event.

Previously, this handler didn't check the connection state and
could call the regular event handler on a connection that was
already in finalization stage.  In the worst case that could
lead to a segmentation fault, since some data structures aren't
supposed to be used during connection finalization.  Particularly,
the waiting queue can contain already freed streams, so the
WINDOW_UPDATE frame received by that moment could trigger
accessing to these freed streams.

Now, the connection error flag is explicitly checked in
ngx_http_v2_handle_connection_handler().

HTTP/2: fixed stream finalization.

2017-03-29T17:16:23+00:00

In order to finalize stream the error flag is set on fake connection and
either "write" or "read" event handler is called.  The read events of fake
connections are always ready, but it's not the case with the write events.

When the ready flag isn't set, the error flag can be not checked in some
cases and as a result stream isn't finalized.  Now the ready flag is
explicilty set on write events for proper finalization in all cases.

HTTP/2: emit PROTOCOL_ERROR on padding errors.

2017-03-26T08:25:05+00:00

Signed-off-by: Piotr Sikora

HTTP/2: fix flow control with padded DATA frames.

2017-03-26T08:25:04+00:00

Previously, flow control didn't account for padding in DATA frames,
which meant that its view of the world could drift from peer's view
by up to 256 bytes per received padded DATA frame, which could lead
to a deadlock.

Signed-off-by: Piotr Sikora

HTTP/2: fix $body_bytes_sent variable.

2017-03-26T08:25:03+00:00

Previously, its value included payloads and frame headers of HEADERS
and CONTINUATION frames.

Signed-off-by: Piotr Sikora