pulp downloaders don't follow 301 redirects when syncing content
The fixtures container is sending a 301 redirect with a location header, but pulp does not make follow up requests.
Updated by firstname.lastname@example.org about 2 years ago
- Status changed from NEW to CLOSED - WORKSFORME
I just realized that this was an environmental problem. The container I was syncing from had it's port 80 mapped to my localhost 8000. So when I was getting a 301 from the container, the location header had port 80 and following the redirect was causing a 404.