-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The handshake time is particularly long in absence of session resumption #288
Comments
500ms sounds suspiciously like a retransmission, so I think to move forward we'd need a client-side QLOG file + a wireshark capture (with SSL keys). |
python examples/http3_client.py -v https://doh3.dns.nextdns.io/info
QLOG file: qlog.log Please forgive me not to provide a complete wireshark capture against leaking possible personally identifiable information.
Moreover, the same issue occurs when connecting "https://cloudflare-dns.com/" and "https://dns.google/". |
As far as I know, pyca/cryptography#7236 is responsible for this issue. Even though cryptography is downgraded to 36.0.2, it still takes about 30 ms to verify certificate. |
Moreover, I prefer system CA certificates to "certifi".
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It is very strange for aioquic to take at least 500 ms to complete handshake, and the following code to illustrate this issue.
python examples/http3_client.py -v https://doh3.dns.nextdns.io/info
The round-trip time of "doh3.dns.nextdns.io" is 30 ms or so, which is seen from
and further verified by
However, in the following two lines, aioquic unexpectedly spends disproportionately approximately 500 ms to verify certificate, compared with 30 ms round-trip time.
From my perspective, the connection time is bound by IO, and thus, it should be instant to verify certificate.
The text was updated successfully, but these errors were encountered: