Stefan Eissing 88a1ab511c ngtcp2: fix handling of blocked stream data ... The stream blocking might not be the one of the current easy handle. Look up the stream to be marked as blocking via its stream_id in the internal hash. Theoretically, this does not have to be one of the h3 streams, so not finding it is not an error. Fixes #18905 Reported-by: Joshua Rogers Closes #18906		2025-10-07 17:24:01 +02:00
..
curl_ngtcp2.c	ngtcp2: fix handling of blocked stream data	2025-10-07 17:24:01 +02:00
curl_ngtcp2.h	build: fix build errors/warnings in rare configurations	2025-07-23 22:17:03 +02:00
curl_osslq.c	osslq: set out idle timeout to 0	2025-10-07 17:23:24 +02:00
curl_osslq.h	build: fix build errors/warnings in rare configurations	2025-07-23 22:17:03 +02:00
curl_quiche.c	lib: stop overriding system printf symbols	2025-10-06 20:57:59 +02:00
curl_quiche.h	build: fix build errors/warnings in rare configurations	2025-07-23 22:17:03 +02:00
vquic-tls.c	lib: stop overriding system printf symbols	2025-10-06 20:57:59 +02:00
vquic-tls.h	http/3: report handshake with version and cipher as for TCP connections	2025-07-14 14:08:32 +02:00
vquic.c	lib: stop overriding system printf symbols	2025-10-06 20:57:59 +02:00
vquic.h	build: fix build errors/warnings in rare configurations	2025-07-23 22:17:03 +02:00
vquic_int.h	ngtcp2: use custom mem funcs	2025-08-18 13:25:52 +02:00