404 error through content proxy due to incorrect location_href
It seems that for some reason the main server and the content proxy can use different schemas for the organization of the packages inside a repository which doesn't always seem to match.
Client accesses content proxy to retrieve the latest kibana rpm:
which results in a 404 for the client.
The content proxy uses the following URL to get the rpm from the main server:
which does not exist. The correct URL would be:
#2 Updated by Gerald Vogt 2 months ago
This issue also affects other repositories like centos7 updates. I have just posted more in the community
For example, access through the proxy to bind-libs
is mapped to the main server URL
which does not exist. The main server has it at
I have just noticed this during a pxe installation test. It's not only bind-libs but according to the logs a total of 133 packages could not be downloaded...