`data->id` is unique in *most* situations, but not in all. If a libcurl application uses more than one connection cache, they will overlap. This is a rare situations, but libcurl apps do crazy things. However, for informative things, like tracing, `data->id` is superior, since it assigns new ids in curl's serial curl_easy_perform() use. Introduce `data->mid` which is a unique identifer inside one multi instance, assigned on multi_add_handle() and cleared on multi_remove_handle(). Use the `mid` in DoH operations and also in h2/h3 stream hashes. Reported-by: 罗朝辉 Fixes #14414 Closes #14499 |
||
|---|---|---|
| .. | ||
| curl_msh3.c | ||
| curl_msh3.h | ||
| curl_ngtcp2.c | ||
| curl_ngtcp2.h | ||
| curl_osslq.c | ||
| curl_osslq.h | ||
| curl_quiche.c | ||
| curl_quiche.h | ||
| vquic_int.h | ||
| vquic-tls.c | ||
| vquic-tls.h | ||
| vquic.c | ||
| vquic.h | ||