From: Allan Clark <firstname.lastname@example.org>
To: Paul Smith <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Possible file download bug?
Date: Fri, 28 Sep 2018 14:22:00 -0000 [thread overview]
Message-ID: <AE65C330-EEC9-4AF7-B958-4E354125CE4A@gmail.com> (raw)
> On Sep 28, 2018, at 06:11, Paul Smith <firstname.lastname@example.org> wrote:
> I wanted to alert you to a possible bug. I'm using someone else's product that uses an old copy of Crossgcc and I've found the following issue, and from looking at the latest Crossgcc code I suspect the same bug still exists.
> The issue is in scripts/functions in the code that downloads a file from the web using wget or curl. My local ISP 'catches' page load errors and returns their own generated HTML error page and the bug I'm seeing results from a file download believing it succeeded when actually it downloaded just a dummy HTML page.
> In my case the files were always supposed to be variants on Linux tar files so it easy to use the Linux 'file' command to see if the file was actually an HTML page. I don't know whether you can do the same or whether the files you are downloaded are more diverse and need more careful checking, perhaps outside of the file download function.
> However I wanted to alert you to this odd behaviour as it soaked up a few hours this morning identifying the cause and a fix.
When the file is not found for download, does the ISP forward a 4xx or 5xx error code, or a 200 as though nothing went wrong?
next prev parent reply other threads:[~2018-09-28 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 13:11 Paul Smith
2018-09-28 14:22 ` Allan Clark [this message]
2018-10-01 7:47 ` Paul Smith
2018-09-28 16:40 ` Alexey Neyman
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).