privacy flag should disable the 'geocoding.query' section

[missinglink]

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

[heffergm]

If the origin receives a request that it deems private, it should return a response that includes a Cache-Control: private header. The edge will then pass the response directly back and not cache it.

[missinglink]

ok cool thanks, I'm guessing that means that any requests coming from the privacy mobile app will bypass cache?

[heffergm]

Assuming they're setting a flag that the backend responds to with a Cache-Control: private header, they should. We can have Chuck dump the output of some requests to confirm.

[riordan]

Do we have confirmation on this?