`curl -v` started to print an excessive amount of output for a TLSv1.3
connection. Is it really useful to get two lines of verbose output for
each chunk of data (sometimes 1B) transferred over a TLS connection?
$ curl -V
curl 7.61.1 (x86_64-redhat-linux-gnu) libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2
On 3/29/2023 3:37 AM, Kamil Dudka via curl-library wrote:
`curl -v` started to print an excessive amount of output for a TLSv1.3
connection. Is it really useful to get two lines of verbose output for
each chunk of data (sometimes 1B) transferred over a TLS connection?
$ curl -V
curl 7.61.1 (x86
On Wed, 29 Mar 2023, Ray Satiro via curl-library wrote:
I don't see that output in curl 8.0.1.
{ [15637 bytes data]
* Connection #0 to host static.snyk.io left intact
Is it perhaps because of this fix?
commit bde24fac7cfd4cb67593cb9b524b6a06ada09f3a
Author: Cherish98 <66007047+cheris...@us
On Wednesday, March 29, 2023 10:20:57 AM CEST Daniel Stenberg via curl-library
wrote:
> On Wed, 29 Mar 2023, Ray Satiro via curl-library wrote:
>
> > I don't see that output in curl 8.0.1.
> >
> > { [15637 bytes data]
> > * Connection #0 to host static.snyk.io left intact
>
> Is it perhaps becau
On Wed, Mar 29, 2023 at 9:37 AM Kamil Dudka via curl-library
wrote:
>
> `curl -v` started to print an excessive amount of output for a TLSv1.3
> connection. Is it really useful to get two lines of verbose output for
> each chunk of data (sometimes 1B) transferred over a TLS connection?
Depending