Scallywag cpuid srcpackage download failure 403 Forbidden

Scallywag cpuid srcpackage download failure 403 Forbidden

[Brian Inglis]

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.

-- 
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.]

Re: Github CI Scallywag Download Failure 403 Forbidden

[Brian Inglis]

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.

-- 
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.]

Re: Github CI Scallywag Download Failure 403 Forbidden

[Jon Turney]

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).

Re: Github CI Scallywag Download Failure 403 Forbidden

[Brian Inglis]

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.]