luckyframework / luckyframework/lucky
Far future expires on static files
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
This will likely be similar to work done in #154. This will build upon that one by adding a far future expires header to static assets
See more on far future expires header: https://developer.yahoo.com/performance/rules.html#expires
We can safely set it for a year since assets are fingerprinted so the cache will be busted as soon as an asset changes. This will really help warm cache page loads
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 the related work in issue #154 and the linked Yahoo performance guidance, then locate the code path that serves static assets. Confirm how fingerprinted assets are handled and identify the relevant tests or test entry point. Done means static assets receive a one-year far-future Expires header without breaking existing asset serving behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100