Backport #8366
closed
Backpot to 2.1: docker 20.10 client pull operation fails with Error response from daemon: missing or empty Content-Type header
Status:
CLOSED - CURRENTRELEASE
- Copied from Issue #8208: docker 20.10 client pull operation fails with Error response from daemon: missing or empty Content-Type header added
- Copied to Backport #8367: Backpot to 2.2: docker 20.10 client pull operation fails with Error response from daemon: missing or empty Content-Type header added
- Status changed from NEW to ASSIGNED
- Assignee changed from dkliban@redhat.com to mdellweg
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint changed from Sprint 90 to Sprint 92
Also available in: Atom
PDF
.
Handle HEAD requests as if they are GET requests
The Content-Type header is stripped by DRF when there is no body in the response.
Django and aiohttp both strip the body of HEAD requests. It is safe to handle HEAD requests the same as GET requests and rely on the web server to strip the body of the response.
This patch also adds the Content-Type header to the ManifestResponse objects which are used when responding to requests of Manifest creation.
fixes #8366 https://pulp.plan.io/issues/8366
backports #8208 https://pulp.plan.io/issues/8208
(cherry picked from commit ceb266c7cb8fefc2efb49ff7cfa9311480d6044a)