Re: HTTP/3 and CURLINFO_TLS_SSL_PTR

Stefan Eissing via curl-library <[email protected]>
Newsgroups gmane.comp.web.curl.library
Message-ID <[email protected]>

> Am 02.07.2025 um 15:49 schrieb Stefan Eissing via curl-library <[email protected]>:
> 
> 
> 
>> Am 02.07.2025 um 15:38 schrieb Larry Campbell via curl-library <[email protected]>:
>> 
>> Context: curl 8.11.1, built with nghttp2/nghttp3/ngtcp2 and openssl.
>> 
>> I use CURLINFO_TLS_SSL_PTR to capture the peer certificate and certificate chain. This works fine with HTTP/1 and HTTP/2. But with HTTP/3, the CURLINFO_TLS_SSL_PTR returns NULL in the curl_tlssessioninfo 'internals' variable. (It does, as expected, return CURLSSLBACKEND_OPENSSL in the 'backend' variable.)
>> 
>> Am I doing something wrong, or is this an inherent limitation of the HTTP/3 implementation?
> 
> This is currently not supported for HTTP/3. More of an oversight, really.
> 
> I created https://github.com/curl/curl/issues/17801 to track this and will work on implementing this for the next version.

FYI: implementation of this feature available at https://github.com/curl/curl/pull/17809

Cheers,
Stefan

> 
> Kind Regards.
> Stefan
> 
>> 
>> - lc
>> 
>> -- 
>> Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
>> Etiquette:   https://curl.se/mail/etiquette.html
> 
> -- 
> Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
> Etiquette:   https://curl.se/mail/etiquette.html

-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.