openstreetmap / openstreetmap/mod_tile
Difficulty to expose metatile as a HTTP response header?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 318
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Description
I am looking at improving caching and purging for tile.openstreetmap.org see: https://github.com/openstreetmap/operations/issues/947
How much effort would it be to expose the source metatile in a HTTP response header?
eg:
Surrogate-Key: meta_z_x_y
The format of z_x_y isn't important. Any logical format is ok.
Would there be a performance impact?
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
The issue names no files or tests; start by tracing how mod_tile constructs tile HTTP responses and identifies the source metatile. Determine where a response header could be added and how its format and performance impact should be validated. Done means tile responses expose a consistent metatile key without unacceptable overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100