privacy flag should disable the 'geocoding.query' section
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 259
- Forks
- 168
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 1
Description
privacy flag should disable the 'geocoding.query' section as it may contain sensitive information such as the input query and the device position.
eg:
"query": {
"text": "strip club",
"private": true,
"focus.point.lat": 40.744243,
"focus.point.lon": -73.990342
}
we also need to ensure that privacy:true requests do not get cached in the edge cache, @heffergm I think this is set up already?
edit: the api should also return the Cache-Control: private header when privacy:true is set
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 in the API request handling for requests with privacy:true, tracing how the geocoding.query section is exposed and how edge-cache behavior is configured. Done means sensitive query and position data are excluded, privacy requests are not cached, and the API returns Cache-Control: private; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100