lp:~titusx/nginx/mainline
- Get this branch:
- bzr branch lp:~titusx/nginx/mainline
Branch merges
Import details
This branch is an import of the HEAD branch of the Git repository at https://github.com/nginx/nginx.git.
Last successful import was .
Recent revisions
- 7302. By Sergey Kandaurov <email address hidden>
-
HTTP/3: fixed handling of zero-length literal field line.
Previously, st->value was passed with NULL data pointer to header handlers.
- 7301. By Roman Arutyunyan <email address hidden>
-
QUIC: ngx_quic_buffer_t use-after-free protection.
Previously the last chain field of ngx_quic_buffer_t could still reference freed
chains and buffers after calling ngx_quic_free_buffer( ). While normally an
ngx_quic_buffer_t object should not be used after freeing, resetting last_chain
field would prevent a potential use-after-free. - 7300. By Roman Arutyunyan <email address hidden>
-
QUIC: ignore CRYPTO frames after handshake completion.
Sending handshake-level CRYPTO frames after the client's Finished message could
lead to memory disclosure and a potential segfault, if those frames are sent in
one packet with the Finished frame. - 7299. By Roman Arutyunyan <email address hidden>
-
HTTP/3: fixed dynamic table overflow.
While inserting a new entry into the dynamic table, first the entry is added,
and then older entries are evicted until table size is within capacity. After
the first step, the number of entries may temporarily exceed the maximum
calculated from capacity by one entry, which previously caused table overflow.The easiest way to trigger the issue is to keep adding entries with empty names
and values until first eviction.The issue was introduced by 987bee4363d1.
- 7298. By Roman Arutyunyan <email address hidden>
-
HTTP/3: decoder stream pre-creation.
Previously a decoder stream was created on demand for sending Section
Acknowledgement, Stream Cancellation and Insert Count Increment. If conditions
for sending any of these instructions never happen, a decoder stream is not
created at all. These conditions include client not using the dynamic table and
no streams abandoned by server (RFC 9204, Section 2.2.2.2). However RFC 9204,
Section 4.2 defines only one condition for not creating a decoder stream:An endpoint MAY avoid creating a decoder stream if its decoder sets
the maximum capacity of the dynamic table to zero.The change enables pre-creation of the decoder stream at HTTP/3 session
initialization if maximum dynamic table capacity is not zero. Note that this
value is currently hardcoded to 4096 bytes and is not configurable, so the
stream is now always created.Also, the change fixes a potential stack overflow when creating a decoder
stream in ngx_http_v3_send_ cancel_ stream( ) while draining a request stream by
ngx_drain_connections( ). Creating a decoder stream involves calling
ngx_get_connection( ), which calls ngx_drain_ connections( ), which will drain the
same request stream again. If client's MAX_STREAMS for uni stream is high
enough, these recursive calls will continue until we run out of stack.
Otherwise, decoder stream creation will fail at some point and the request
stream connection will be drained. This may result in use-after-free, since
this connection could still be referenced up the stack. - 7297. By Sergey Kandaurov <email address hidden>
-
QUIC: client transport parameter data length checking.
- 7296. By J Carter <email address hidden>
-
Upstream: variables support in proxy_limit_rate and friends.
- 7295. By Roman Arutyunyan <email address hidden>
-
Optimized chain link usage (ticket #2614).
Previously chain links could sometimes be dropped instead of being reused,
which could result in increased memory consumption during long requests.A similar chain link issue in ngx_http_
gzip_filter_ module was fixed in
da46bfc484ef (1.11.10).Based on a patch by Sangmin Lee.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)