rust-lang / rust-lang/simpleinfra
Cloudfront cache not cleared for database dumps with Accept-Encoding request headers
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 178
- Forks
- 107
- Avg merge
- 15h 57m
- Merged PRs (30d)
- 38
Description
Not trying to bump a closed issue thread, but I'm also not sure if this is related. I'm being served a stale version of the dump when I don't provide a Accept-Encoding header:
Setting Accept-Encoding to gzip, deflate, br grabs me the new data, but I'm actually not sure if that's just related to how cloudfront is caching the request.
Is there any way around cloudfront's cache or should I just expect to possibly have ~48-hour stale data?
Originally posted by @enricozb in https://github.com/rust-lang/crates.io/issues/6652#issuecomment-1676432689
(opening per @jdno's suggestion)
Contributor guide
No contributing guide indexed for this repository
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 the CloudFront configuration serving the database dumps and compare cache behavior for requests with and without Accept-Encoding. Reproduce both request variants, then verify that the configuration prevents unexpectedly stale data or documents the expected cache delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100