Open matthiasblaesing opened 2 years ago
Thank you for bringing this to our attention.
We will investigate and see if we can change this behavior without causing other issues.
To work around this issue I now used a local apache server to filter out the broken URL. I create a local proxy (first line ensures the media.1/media
url generates a 404, and in other cases proxies to the repository):
ProxyPass /corretto/x86_64/media.1/media https://HOSTNAME/notexisting
ProxyPass /corretto https://yum.corretto.aws
and use that with the corresponding repo definition:
[AmazonCorretto]
name=Amazon Corretto
baseurl=https://HOSTNAME/corretto/$basearch
enabled=1
gpgkey=https://yum.corretto.aws/corretto.key
gpgcheck=1
While that works, it is not a solution for a production system.
Installation of Amazon Corretto on SLES 12.5 fails when the repositories are refreshed. The issue seems to be, that the repository returns an access denied error for the URL:
https://yum.corretto.aws/x86_64/media.1/media
In newer versions rpm seems to ignore the access denied error, but the version from SLES 12.5 shows this behaviour:
To Reproduce
sudo zypper addrepo https://yum.corretto.aws/corretto.repo
sudo zypper refresh
and accept the unknown repository keysudo zypper -v refresh
Result:
If refresh is forced, it will work, but that is not a good state to run in production.
Expected behavior
No error is reported, the repository data is up-to-date.
Additional infos
This issue from SuSE diagnoses, that the server should return a 404 for a non existing path and not 403, which sound reasonable:
https://bugzilla.opensuse.org/show_bug.cgi?id=1032348
Maybe the directory settings just need to be changed, so that not existing files are reported as not existing files.