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: Expected behaviour of CURL_ALTSVC_HTTP and --proxy
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Fabian Keil via curl-library <curl-library_at_lists.haxx.se>
Date: Mon, 23 May 2022 15:25:02 +0200
Daniel Stenberg <daniel_at_haxx.se> wrote on 2022-05-23 at 00:25:19:
> On Sat, 21 May 2022, Fabian Keil via curl-library wrote:
>
> > The recently added tests 412 and 413 fail when using Privoxy as proxy.
> >
> > Looking at the trace output it seems that curl is tunnelling
> > the requests when --proxy is being used even though it's vanilla
> > http:// and not https://:
>
> ...
>
> > Is that the expected behaviour or a bug?
>
> It sounds like a bug. But we only allow alt-svc for HTTP in debug-builds (with
> the necessary environment variable set) for testing, so in a release build
> this would never happen...
Looking into this some more I noticed another issue in the log:
14:12:58.974144 == Info: Alt-svc connecting from [h1]whohoo.:12345 to [h1]127.0.0.1:20000
[...]
14:12:58.980989 => Send header, 111 bytes (0x6f)
0000: GET /412 HTTP/1.1
0013: Host: whohoo.:12345
If I'm not mistaken this should actually be "Host: 127.0.0.1:20000".
However, as you already mentioned, this indeed only affects the debug build.
Fabian
Received on 2022-05-23
Date: Mon, 23 May 2022 15:25:02 +0200
Daniel Stenberg <daniel_at_haxx.se> wrote on 2022-05-23 at 00:25:19:
> On Sat, 21 May 2022, Fabian Keil via curl-library wrote:
>
> > The recently added tests 412 and 413 fail when using Privoxy as proxy.
> >
> > Looking at the trace output it seems that curl is tunnelling
> > the requests when --proxy is being used even though it's vanilla
> > http:// and not https://:
>
> ...
>
> > Is that the expected behaviour or a bug?
>
> It sounds like a bug. But we only allow alt-svc for HTTP in debug-builds (with
> the necessary environment variable set) for testing, so in a release build
> this would never happen...
Looking into this some more I noticed another issue in the log:
14:12:58.974144 == Info: Alt-svc connecting from [h1]whohoo.:12345 to [h1]127.0.0.1:20000
[...]
14:12:58.980989 => Send header, 111 bytes (0x6f)
0000: GET /412 HTTP/1.1
0013: Host: whohoo.:12345
If I'm not mistaken this should actually be "Host: 127.0.0.1:20000".
However, as you already mentioned, this indeed only affects the debug build.
Fabian
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
- application/pgp-signature attachment: OpenPGP digital signature