User buckets: URLs for brows/thumbnail images, products, and logs may 403
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
Research direction
The issue proposes documenting that URLs for browse images, thumbnails, products, and logs can return 403 when user buckets are private. Read the job response handling and the get-files step mentioned in the issue to confirm which bucket, prefix, and key details are provided. Done means the behavior and its implications for clients are documented, with the issue marked wontfix.
Written by the indexing model from the issue text.
Description
We include URLs for browse/thumbnail images, product files, and log files, but they will return 403 - Access Denied errors when end-user buckets are not public.
The S3 bucket and prefix are provided in the job response, and for product files, the S3 bucket and Key is also specified, so users with private buckets should still know where the products are and how to access them.
Clients like Vertex, however, will need to handle 403 - Access Denied errors when accessing these URLs.
We could, alternatively, copy browse images/thumbnails/logs to the HyP3 content bucket in the get-files step and provide those URLs in the jobs response, but then we'd report different locations for files, which could be confusing, or more importantly, expiration times of these files may not match the reported expiration time.
So I'm inclined to leave this as open with a 'wontfix` label to document this behavior for users.
- Dominant language
- Python
- Stars
- 53
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from ASFHyP3/hyp3
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Most static tests fail when a date-like string is provided as an example value in a job spec YAMLOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Jira Bug
Difficulty 1/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
FinanceFlash/unvibecode#699 ·
Maintainers usually reply within 1 day
-
enhancement Website
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/OWASP-Hunting#96 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
micropython/micropython#19942 ·
Maintainers usually reply within 1 day
-
A rebuild posts "not part of this build" success to the commit's failed `nix-build` gate and effectsPossibly taken @Padraic-O-Mhuiris claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`epoch.Integer` raises a raw OverflowError for integers too large to convert to a floatPossibly taken @arindam77 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-extra-types#479 ·
Maintainers usually reply within 1 day