Downloading packages from browser gives me a hash as package name when using GCS as backend
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
3.87.0
Describe the bug
The same as https://github.com/pulp/pulpcore/issues/3124, but when using GCS as backend. I can't use signed URLs due to #6917. When signed URLs are not used, GCS will set the content-disposition headers in response only if it is set as a metadata in the blob directly as part of upload, and I don't think Pulp does it.
To Reproduce
Use GCS as storage backend, upload a content, and try to download it from browser.
Expected behavior
The actual file name gets used, not the object storage hash
Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
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 reading pulpcore issue #3124 and reviewing how the GCS storage backend handles downloads when signed URLs are disabled, including the related constraint in issue #6917. Reproduce the browser download with GCS, then verify that the response uses the actual package filename instead of the object hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100