Project

Profile

Help

Issue #9216

closed

S3 storage always sets Content-Type header to octet-stream

Added by gerrod over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 103
Quarter:

Description

Since artifact files are renamed to the form of artifact/sh/a256digest when being saved, artifacts stored on s3 will always be returned from the content app with Content-Type header application/octet-stream. For most artifacts this is fine, but for PublishedMetadata which is stored through a PublishedArtifact this can be problematic if a content type's tooling is expecting that metadata to be served with a certain Content-Type header. As is the case for pip which expects simple index html pages to have the Content-Type header text/html.


Related issues

Copied to Pulp - Backport #9244: Backport #9216 "S3 storage always sets Content-Type header to octet-stream" to 3.14.zCLOSED - CURRENTRELEASE

Actions

Also available in: Atom PDF