Content-Disposition header not always set
Open
Nobody has claimed this yet.
Issue
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
3.20.0 and probably earlier
Describe the bug
Content-Disposition header is not set by pulpcore-content when serving content from the local filesystem.
Content-Disposition header is not set by pulpcore-cotent when streaming a response for on_demand or streamed content.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how pulpcore-content serves content from the local filesystem and how responses are streamed for on_demand and streamed content. No source file or test is named in the issue, so locate those entry points first. Done means Content-Disposition is set consistently for each described serving path, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100