#5759 Set up a 302 redirect for blobs from registry.fpo to cdn.registry.fpo
Closed: Fixed Opened by bowlofeggs.

The last step in getting Fedora's container blobs scalable is to set up a 302 redirect on API calls that try to GET container blobs from registry.fedoraproject.org. The API calls will be of the form GET /v2/<name>/blobs/<digest>, where <name> can contain slashes. Here is an example request:

GET /v2/fedora/blobs/sha256:38bfcb68fb3809dd206661bcc22ad42601da87d12a8ff259b044b0f42c4f4d3a

Here are details on the GET Blob call:

https://docs.docker.com/registry/spec/api/#/blob

We would like to have this in place for the Fedora 26 alpha freeze, so it would be nice to get it done sometime in the next week or so if possible. Thanks!


This Taiga card also tracks this task: https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/745

This is live now.

Metadata Update from @puiterwijk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

It works!

$ http https://registry.fedoraproject.org/v2/fedora/randy2.0/blobs/sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4
HTTP/1.1 302 Found
Connection: Keep-Alive
Content-Length: 429
Content-Type: text/html; charset=iso-8859-1
Date: Wed, 15 Feb 2017 16:35:12 GMT
Keep-Alive: timeout=15, max=500
Location: https://cdn.registry.fedoraproject.org/v2/fedora/randy2.0/blobs/sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4
Server: Apache/2.4.6 (Red Hat Enterprise Linux)
Strict-Transport-Security: max-age=15768000; includeSubDomains; preload
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://cdn.registry.fedoraproject.org/v2/fedora/randy2.0/blobs/sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4">here</a>.</p>
<hr>
<address>Apache/2.4.6 (Red Hat Enterprise Linux) Server at registry.fedoraproject.org Port 443</address>
</body></html>
Metadata