Mercurial > hg > nginx
comparison src/event/quic/ngx_event_quic_connection.h @ 9189:fcec773dd249
QUIC: avoid partial expansion of PATH_CHALLENGE/PATH_RESPONSE.
By default packets with these frames are expanded to 1200 bytes. Previously,
if anti-amplification limit did not allow this expansion, it was limited to
whatever size was allowed. However RFC 9000 clearly states no partial
expansion should happen in both cases.
Section 8.2.1. Initiating Path Validation:
An endpoint MUST expand datagrams that contain a PATH_CHALLENGE frame
to at least the smallest allowed maximum datagram size of 1200 bytes,
unless the anti-amplification limit for the path does not permit
sending a datagram of this size.
Section 8.2.2. Path Validation Responses:
An endpoint MUST expand datagrams that contain a PATH_RESPONSE frame
to at least the smallest allowed maximum datagram size of 1200 bytes.
...
However, an endpoint MUST NOT expand the datagram containing the
PATH_RESPONSE if the resulting data exceeds the anti-amplification limit.
| author | Roman Arutyunyan <arut@nginx.com> |
|---|---|
| date | Wed, 29 Nov 2023 18:13:25 +0400 |
| parents | 2880f60a80c3 |
| children | a6f79f044de5 |
comparison
equal
deleted
inserted
replaced
| 9188:b05c622715fa | 9189:fcec773dd249 |
|---|---|
| 104 size_t mtu; | 104 size_t mtu; |
| 105 size_t mtud; | 105 size_t mtud; |
| 106 size_t max_mtu; | 106 size_t max_mtu; |
| 107 off_t sent; | 107 off_t sent; |
| 108 off_t received; | 108 off_t received; |
| 109 u_char challenge1[8]; | 109 u_char challenge[2][8]; |
| 110 u_char challenge2[8]; | |
| 111 uint64_t seqnum; | 110 uint64_t seqnum; |
| 112 uint64_t mtu_pnum[NGX_QUIC_PATH_RETRIES]; | 111 uint64_t mtu_pnum[NGX_QUIC_PATH_RETRIES]; |
| 113 ngx_str_t addr_text; | 112 ngx_str_t addr_text; |
| 114 u_char text[NGX_SOCKADDR_STRLEN]; | 113 u_char text[NGX_SOCKADDR_STRLEN]; |
| 115 ngx_uint_t validated; /* unsigned validated:1; */ | 114 ngx_uint_t validated; /* unsigned validated:1; */ |