All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Maier,
	Brandon L                            Collins"
	<Brandon.Maier@collins.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] [PATCH 1/2] support/download: introduce curl backend for FTP transfers
Date: Tue, 21 May 2024 19:07:32 +0200	[thread overview]
Message-ID: <ZkzU1M_pN0C-zcUr@landeda> (raw)
In-Reply-To: <BN0P110MB1673D23A6CFB29DDA9C61DA5EBEAA@BN0P110MB1673.NAMP110.PROD.OUTLOOK.COM>

Brandon, All,

On 2024-05-21 16:19 +0000, Maier, Brandon L                            Collins spake thusly:
> > From: buildroot <buildroot-bounces@buildroot.org> On Behalf Of Yann E.
> > MORIN
[--SNIP--]
> > +config BR2_CURL
> > +     string "Curl command"
> > +     default "curl -q --ftp-pasv --retry 3"
> 
> In my testing I found we need `-L`/`--location` which allows curl to
> follow redirects. Otherwise, some URLs like github tarballs will silently
> fail to download.
> 
> Also I'd suggest `-f`/`--fail` which allows curl to detect some HTTP 4XX
> errors and print them to stderr.

The curl backend is only supposed to handle ftp and ftps URIs, not http
or https. See that part in the download wrapper:

   92         case "${backend}" in
   93             git|svn|cvs|bzr|file|scp|hg|sftp) ;;
   94             ftp|ftps) backend="curl" ;;
   95             *) backend="wget" ;;
   96         esac

So, unless I borked something, curl should not be used for http or
https.

If you have a reproducer, I'm all eyes to test here and fix the
breakage.

Thanks for the feedback, much appreciated! 👍

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-21 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 20:25 [Buildroot] [PATCH 0/2] support/download: fix running on hosts with wget2 (branch yem/dl-curl) Yann E. MORIN
2024-05-18 20:25 ` [Buildroot] [PATCH 1/2] support/download: introduce curl backend for FTP transfers Yann E. MORIN
2024-05-19  7:46   ` Yann E. MORIN
2024-05-21 16:19   ` [Buildroot] [External] " Maier, Brandon L Collins via buildroot
2024-05-21 17:07     ` Yann E. MORIN [this message]
2024-05-21 17:15       ` Maier, Brandon L Collins via buildroot
2024-05-18 20:25 ` [Buildroot] [PATCH 2/2] utils/genrandconfig: do not check certificates with curl Yann E. MORIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZkzU1M_pN0C-zcUr@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=Brandon.Maier@collins.com \
    --cc=buildroot@buildroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.