Commit d2a313b
committed
BUG/MINOR: quic: ignore AGAIN ncbuf err when parsing CRYPTO frames
This fix follows this previous one:
BUG/MINOR: quic: reorder fragmented RX CRYPTO frames by their offsets
which is not sufficient when a client fragments and mixes its CRYPTO frames AND
leaveswith holes by packets. ngtcp2 (and perhaps chrome) splits theire CRYPTO
frames but without hole by packet. In such a case, the CRYPTO parsing leads to
QUIC_RX_RET_FRM_AGAIN errors which cannot be fixed when the peer resends its packets.
Indeed, even if the peer resends its frames in a different order, this does not
help because since the previous commit, the CRYPTO frames are ordered on haproxy side.
This issue was detected thanks to the interopt tests with quic-go as client. This
client fragments its CRYPTO frames, mixes them, and generate holes, and most of
the times with the retry test.
To fix this, when a QUIC_RX_RET_FRM_AGAIN error is encountered, the CRYPTO frames
parsing is not stop. This leaves chances to the next CRYPTO frames to be parsed.
Must be backported as far as 2.6 as the commit mentioned above.1 parent 2c351df commit d2a313b
1 file changed
+6
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3249 | 3249 | | |
3250 | 3250 | | |
3251 | 3251 | | |
3252 | | - | |
| 3252 | + | |
3253 | 3253 | | |
3254 | 3254 | | |
3255 | 3255 | | |
| |||
3514 | 3514 | | |
3515 | 3515 | | |
3516 | 3516 | | |
3517 | | - | |
3518 | | - | |
3519 | | - | |
| 3517 | + | |
| 3518 | + | |
3520 | 3519 | | |
3521 | 3520 | | |
3522 | 3521 | | |
| |||
3534 | 3533 | | |
3535 | 3534 | | |
3536 | 3535 | | |
| 3536 | + | |
| 3537 | + | |
| 3538 | + | |
3537 | 3539 | | |
3538 | 3540 | | |
3539 | 3541 | | |
| |||
0 commit comments