Stefan Eissing 21fd64645b quic: no local idle connection timeout, ngtcp2 keep-alive ... Do not set a transport parameter idle timeout, meaning we have no such thing from our side. The remote setting then applies. In ngtcp2, set its "keep-alive" timer to prevent a possible remote idle timeout to tear down the connection while we have active transfers on that connection. Closes #17057		2025-04-18 23:52:51 +02:00
..
.checksrc	strparse: switch to curl_off_t as base data type	2025-02-15 21:58:48 +01:00
curl_msh3.c	multi: do transfer book keeping using mid	2025-04-17 17:28:38 +02:00
curl_msh3.h	lib: include files using known path	2025-04-08 17:00:00 +02:00
curl_ngtcp2.c	quic: no local idle connection timeout, ngtcp2 keep-alive	2025-04-18 23:52:51 +02:00
curl_ngtcp2.h	vquic: ngtcp2 + openssl support	2025-04-16 22:32:07 +02:00
curl_osslq.c	quic: no local idle connection timeout, ngtcp2 keep-alive	2025-04-18 23:52:51 +02:00
curl_osslq.h	lib: include files using known path	2025-04-08 17:00:00 +02:00
curl_quiche.c	quic: no local idle connection timeout, ngtcp2 keep-alive	2025-04-18 23:52:51 +02:00
curl_quiche.h	lib: include files using known path	2025-04-08 17:00:00 +02:00
vquic-tls.c	lib: include files using known path	2025-04-08 17:00:00 +02:00
vquic-tls.h	lib: include files using known path	2025-04-08 17:00:00 +02:00
vquic.c	vquic: ngtcp2 + openssl support	2025-04-16 22:32:07 +02:00
vquic.h	vquic: ngtcp2 + openssl support	2025-04-16 22:32:07 +02:00
vquic_int.h	quic: no local idle connection timeout, ngtcp2 keep-alive	2025-04-18 23:52:51 +02:00