gin-contrib / gin-contrib/cache
Please include the host when generating cache keys.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 456
- Forks
- 100
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
For example, in a multi-tenant scenario, the same Gin application instance might handle requests for both a.example.com and b.example.com. Therefore, the cached result when a user accesses a.example.com/index.html must be distinct from the result for b.example.com/index.html.
Thanks.
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 locating the cache-key generation entry point and its existing tests in the repository. Trace how the request URL is used to build a key, then verify that requests for the same path on different hosts produce distinct cached results. Done means hostnames are included without breaking existing cache behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100