From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Github CI Scallywag Download Failure 403 Forbidden
Date: Sat, 2 Jul 2022 11:26:37 -0600 [thread overview]
Message-ID: <1895dfe0-0a4d-0979-827b-a9e146f0d522@SystematicSw.ab.ca> (raw)
In-Reply-To: <4d4f3aed-88e3-b169-b17d-1e0666d74dab@dronecode.org.uk>
On 2022-07-02 07:01, Jon Turney wrote:
> On 01/07/2022 01:32, Brian Inglis wrote:
>> On 2022-06-26 22:46, Brian Inglis wrote:
>>> Scallywag failing on a plain HTTP non-httpS download.
>>> Ran twice same symptom - 403 Forbidden.
>>>
>>>> scallywag: running 'cygport download srcpackage'
>>>> --2022-06-25 17:14:40--
>>>> http://etallen.com/cpuid/cpuid-20220620.src.tar.gz
>>>> Resolving etallen.com (etallen.com)... 69.65.28.126
>>>> Connecting to etallen.com (etallen.com)|69.65.28.126|:80... connected.
>>>> HTTP request sent, awaiting response... 403 Forbidden
>>>> 2022-06-25 17:14:40 ERROR 403: Forbidden.
>>>> *** ERROR: wget http://etallen.com/cpuid/cpuid-20220620.src.tar.gz
>>>> failed
>>>> Error: Process completed with exit code 1.
>>>
>>> Use to work just fine with previous releases.
>>> Works just fine on my local system multiple ways and times.
>>>
>>> Has anyone seen anything indicating there could be problems with
>>> Github access to upstream or any use it makes of a proxy?
>>>
>>> I will raise the issue with the upstream to see if they are aware of
>>> any issues of that type.
>>
>> Still failing after site owner updated cert.
> This is not certificate issue.
>
> 403 means that the URL was valid, but the server refuses to give it to
> us by policy (often that means that the IP or user-agent is banned).
Thanks Jon,
Latest attempt successfully downloaded for src package build but failed
for binary package builds!
Could the problem be too many downloads of the same file from the same
IP close together?
Any chance that each CI job could share the cached downloads across that
job's builds like cygport?
Upstream has not yet got back again, so I will add this info.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-07-02 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 4:46 Scallywag cpuid srcpackage download failure " Brian Inglis
2022-07-01 0:32 ` Github CI Scallywag Download Failure " Brian Inglis
2022-07-02 13:01 ` Jon Turney
2022-07-02 17:26 ` Brian Inglis [this message]
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=1895dfe0-0a4d-0979-827b-a9e146f0d522@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/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 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).