Issue #9216: S3 storage always sets Content-Type header to octet-stream - Pulp

Actions

Send by e-mail Copy link

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:

gerrod

Category:

Sprint/Milestone:

3.15.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

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