Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Built curl successfully, but no handshake message in verbose output
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: David Hu via curl-users <curl-users_at_cool.haxx.se>
Date: Tue, 23 Mar 2021 23:38:25 +0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello all,
I have built curl with nghttp2, brotli, zstd, librtmp, libgsl, libmetalink, libgasl, libidn2, libssh2 as well as Quiche HTTP3 and using BoringSSL library. Enabled features: HSTS, DoH HTTP2 and HTTP3. However when I tried \`curl --http2-prior-knowledge <url>\` on a HTTP/2 supported URL it is not even showing the familiar \`TLSv1.3, (OUT), TLS handshake, Client Hello (1): ......\` TLS handshake messages anymore. After the \`\*successfully set certificate verify locations...... \*CAFile...... \*CAPath......\` messages it just jumps straight to \`> GET / HTTP/2\` ! It is not behaving as the way that was intended (showing the handshake). I tried Googling around but unfortuantely comes up with nothing relevant. Do you guys know the cause and how to solve it? Thank you very much!
Regards,
David
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wpYEARYIACcFAmBae/AJEIhHxE11w9o4FiEENAqEjUMzaHPUj12tiEfETXXD
2jgAIQkQiEfETXXD2jgWIQQ0CoSNQzNoc9SPXa2IR8RNdcPaOADEAQCEjq0P
eluxo8EKCfu9dpJSx/fogB2nBrgg1Ixh2XqMvwD/QktjQcVf9p039n8Uk8Y/
E2KWaEHsWbm2MmMCy7OplgQ=
=mg6c
-----END PGP SIGNATURE-----
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2021-03-24
Date: Tue, 23 Mar 2021 23:38:25 +0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello all,
I have built curl with nghttp2, brotli, zstd, librtmp, libgsl, libmetalink, libgasl, libidn2, libssh2 as well as Quiche HTTP3 and using BoringSSL library. Enabled features: HSTS, DoH HTTP2 and HTTP3. However when I tried \`curl --http2-prior-knowledge <url>\` on a HTTP/2 supported URL it is not even showing the familiar \`TLSv1.3, (OUT), TLS handshake, Client Hello (1): ......\` TLS handshake messages anymore. After the \`\*successfully set certificate verify locations...... \*CAFile...... \*CAPath......\` messages it just jumps straight to \`> GET / HTTP/2\` ! It is not behaving as the way that was intended (showing the handshake). I tried Googling around but unfortuantely comes up with nothing relevant. Do you guys know the cause and how to solve it? Thank you very much!
Regards,
David
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wpYEARYIACcFAmBae/AJEIhHxE11w9o4FiEENAqEjUMzaHPUj12tiEfETXXD
2jgAIQkQiEfETXXD2jgWIQQ0CoSNQzNoc9SPXa2IR8RNdcPaOADEAQCEjq0P
eluxo8EKCfu9dpJSx/fogB2nBrgg1Ixh2XqMvwD/QktjQcVf9p039n8Uk8Y/
E2KWaEHsWbm2MmMCy7OplgQ=
=mg6c
-----END PGP SIGNATURE-----
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
- application/pgp-keys attachment: publickey_-_EmailAddress_s_D4v1d_4n0_at_protonmail.ch__-_0x340A848D.asc
- application/pgp-signature attachment: publickey_-_EmailAddress_s_D4v1d_4n0_at_protonmail.ch__-_0x340A848D.asc.sig