You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Luca Toscano (Jira)" <ji...@apache.org> on 2022/01/11 14:16:00 UTC
[jira] [Created] (BIGTOP-3630) Some repositories yield to HTTP 403
Luca Toscano created BIGTOP-3630:
------------------------------------
Summary: Some repositories yield to HTTP 403
Key: BIGTOP-3630
URL: https://issues.apache.org/jira/browse/BIGTOP-3630
Project: Bigtop
Issue Type: Bug
Reporter: Luca Toscano
Hi everybody,
at Wikimedia we use reprepro to manage our internal Debian APT repository, in which we sync/copy package from Bigtop's. Today I noticed a weird issue, namely:
{code}
aptmethod error receiving 'http://repos.bigtop.apache.org/releases/1.5.0/debian/10/amd64/dists/bigtop/InRelease': '403 Forbidden [IP: 52.216.83.32 80]'
{code}
If I swap the config from repos.bigtop.apache.org to repo.bigtop.apache.org.s3.amazonaws.com, everything works fine.
The value repo.bigtop.apache.org.s3.amazonaws.com comes from the S3 config, and it is the first CNAME of repos.bigtop.apache.org:
{code}
$ dig repos.bigtop.apache.org +short
repo.bigtop.apache.org.s3.amazonaws.com.
s3-1-w.amazonaws.com.
s3-w.us-east-1.amazonaws.com.
52.216.132.251
{code}
Could it be that our new S3 config needs to be called repos.bigtop.apache.org.s3.amazonaws.com (see the extra s - repoS) to make everything working?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)