nginx.git/src/http/v3, branch release-1.25.0

HTTP/3: removed server push support.

2023-05-12T06:02:10+00:00

QUIC: style.

2023-05-11T15:48:01+00:00

HTTP/3: removed "http3" parameter of "listen" directive.

2023-05-11T09:22:10+00:00

The parameter has been deprecated since c851a2ed5ce8.

QUIC: removed "quic_mtu" directive.

2023-05-11T06:37:51+00:00

The directive used to set the value of the "max_udp_payload_size" transport
parameter.  According to RFC 9000, Section 18.2, the value specifies the size
of buffer for reading incoming datagrams:

    This limit does act as an additional constraint on datagram size in
    the same way as the path MTU, but it is a property of the endpoint
    and not the path; see Section 14. It is expected that this is the
    space an endpoint dedicates to holding incoming packets.

Current QUIC implementation uses the maximum possible buffer size (65527) for
reading datagrams.

HTTP/3: fixed ngx_http_v3_init_session() error handling.

2023-05-04T11:52:22+00:00

A QUIC connection is not usable yet at this early stage of spin up.

HTTP/3: fixed CANCEL_PUSH handling.

2023-04-06T14:18:41+00:00

HTTP/3: "quic" parameter of "listen" directive.

2023-02-27T10:00:56+00:00

Now "listen" directve has a new "quic" parameter which enables QUIC protocol
for the address.  Further, to enable HTTP/3, a new directive "http3" is
introduced.  The hq-interop protocol is enabled by "http3_hq" as before.
Now application protocol is chosen by ALPN.

Previously used "http3" parameter of "listen" is deprecated.

HTTP/3: insert count block timeout.

2023-01-05T15:03:22+00:00

Previously, there was no timeout for a request stream blocked on insert count,
which could result in infinite wait.  Now client_header_timeout is set when
stream is first blocked.

HTTP/3: trigger 400 (Bad Request) on stream error while blocked.

2023-01-05T14:15:46+00:00

Previously, stream was closed with NGX_HTTP_CLOSE.  However, in a similar case
when recv() returns eof or error, status 400 is triggered.

HTTP/3: fixed $connection_time.

2023-01-10T13:59:16+00:00

Previously, start_time wasn't set for a new stream.
The fix is to derive it from the parent connection.
Also it's used to simplify tracking keepalive_time.