We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
curl --verbose displays logs output:
curl --verbose
$ curl -I --verbose https://tradingstrategy.ai * Trying 2606:4700:20::ac43:491e:443... * Connected to tradingstrategy.ai (2606:4700:20::ac43:491e) port 443 (#0) * ALPN: offers h2 * ALPN: offers http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN: server accepted h2 * Server certificate: * subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com * start date: Jun 28 00:00:00 2022 GMT * expire date: Jun 27 23:59:59 2023 GMT * subjectAltName: host "tradingstrategy.ai" matched cert's "tradingstrategy.ai" * issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3 * SSL certificate verify ok. * Using HTTP2, server supports multiplexing * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * h2h3 [:method: HEAD] * h2h3 [:path: /] * h2h3 [:scheme: https] * h2h3 [:authority: tradingstrategy.ai] * h2h3 [user-agent: curl/7.85.0] * h2h3 [accept: */*] * Using Stream ID: 1 (easy handle 0x13b011a00) > HEAD / HTTP/2 > Host: tradingstrategy.ai > user-agent: curl/7.85.0 > accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 256)! < HTTP/2 103 HTTP/2 103 < link: <./_app/immutable/assets/_layout-7ed14c6c.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/TradingDataInfoRow-028f36b2.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/TradingEntityHit-bf38e9c9.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/_page-fa48a47b.css>; as=style; nopush; rel=preload link: <./_app/immutable/assets/_layout-7ed14c6c.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/TradingDataInfoRow-028f36b2.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/TradingEntityHit-bf38e9c9.css>; as=style; nopush; rel=preload, <./_app/immutable/assets/_page-fa48a47b.css>; as=style; nopush; rel=preload < HTTP/2 200 HTTP/2 200 < date: Sat, 15 Oct 2022 10:15:27 GMT date: Sat, 15 Oct 2022 10:15:27 GMT
Hurl should be able to display those logs too (maybe using --very-verbose or a new --very-very-verbose option ?)
--very-verbose
--very-very-verbose
The text was updated successfully, but these errors were encountered:
jcamiel
Successfully merging a pull request may close this issue.
curl --verbose
displays logs output:Hurl should be able to display those logs too (maybe using
--very-verbose
or a new--very-very-verbose
option ?)The text was updated successfully, but these errors were encountered: