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.
Re: CURLINFO_APPCONNECT_TIME_T in HTTP 2
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Babacar Ndiaye via curl-library <curl-library_at_lists.haxx.se>
Date: Mon, 29 May 2023 11:28:50 -0400
We are using version 7.81.0.
I'll dig into this piece to see if that is what is happening:
"or if a new connection with the need to re-authenticate at the proxy is
done"
I didn't question the assumption it's cached. Thanks for pointing that out.
On Sat, May 27, 2023 at 6:14 AM Stefan Eissing via curl-library <
curl-library_at_lists.haxx.se> wrote:
> Addendum: I speak of a recent curl version. If you use an older libcurl,
> please state the version.
>
> > Am 27.05.2023 um 12:00 schrieb Stefan Eissing via curl-library <
> curl-library_at_lists.haxx.se>:
> >
> >
> >
> >> Am 26.05.2023 um 23:22 schrieb Babacar Ndiaye via curl-library <
> curl-library_at_lists.haxx.se>:
> >>
> >> Hi:
> >>
> >> The setup we have is TLS in TLS HTTPS with proxy client authentication.
> As suggested in the docs, we create one multi handler, keep it around to
> leverage the connection caching, and keep adding/removing easy handles to
> service the requests.
> >>
> >> When the transfer is done with HTTP 1.1, what I get out of
> CURLINFO_APPCONNECT_TIME_T with curl_easy_getinfo() makes sense to me.
> Since there is connection reuse, the average is low (100 microsec).
> >>
> >> Now when the transfer is done with HTTP 2, that average is big (200
> millisec). When I do it the other way, make/destroy one easy for each
> request, I get that same 200 millisec.
> >>
> >> Does CURLINFO_APPCONNECT_TIME_T mean the same thing for in HTTP 1.1 and
> 2?
> >
> > Yes, it is the time for handshaking the connection to the origin, not
> the proxy, server. It's the same code for both HTTP versions.
> >
> > The question is then if the connection gets reused in your setup as you
> think it should, or if a new connection with the need to re-authenticate at
> the proxy is done. That would be my suspicion here.
> >
> > Kind Regards,
> > Stefan
> >
> >
> >
> >>
> >> Thanks for your help.
> >> --
> >> 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
>
Date: Mon, 29 May 2023 11:28:50 -0400
We are using version 7.81.0.
I'll dig into this piece to see if that is what is happening:
"or if a new connection with the need to re-authenticate at the proxy is
done"
I didn't question the assumption it's cached. Thanks for pointing that out.
On Sat, May 27, 2023 at 6:14 AM Stefan Eissing via curl-library <
curl-library_at_lists.haxx.se> wrote:
> Addendum: I speak of a recent curl version. If you use an older libcurl,
> please state the version.
>
> > Am 27.05.2023 um 12:00 schrieb Stefan Eissing via curl-library <
> curl-library_at_lists.haxx.se>:
> >
> >
> >
> >> Am 26.05.2023 um 23:22 schrieb Babacar Ndiaye via curl-library <
> curl-library_at_lists.haxx.se>:
> >>
> >> Hi:
> >>
> >> The setup we have is TLS in TLS HTTPS with proxy client authentication.
> As suggested in the docs, we create one multi handler, keep it around to
> leverage the connection caching, and keep adding/removing easy handles to
> service the requests.
> >>
> >> When the transfer is done with HTTP 1.1, what I get out of
> CURLINFO_APPCONNECT_TIME_T with curl_easy_getinfo() makes sense to me.
> Since there is connection reuse, the average is low (100 microsec).
> >>
> >> Now when the transfer is done with HTTP 2, that average is big (200
> millisec). When I do it the other way, make/destroy one easy for each
> request, I get that same 200 millisec.
> >>
> >> Does CURLINFO_APPCONNECT_TIME_T mean the same thing for in HTTP 1.1 and
> 2?
> >
> > Yes, it is the time for handshaking the connection to the origin, not
> the proxy, server. It's the same code for both HTTP versions.
> >
> > The question is then if the connection gets reused in your setup as you
> think it should, or if a new connection with the need to re-authenticate at
> the proxy is done. That would be my suspicion here.
> >
> > Kind Regards,
> > Stefan
> >
> >
> >
> >>
> >> Thanks for your help.
> >> --
> >> 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
>
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-05-29