fix(places): make no-store the default and refuse an unreadable Places 200

Every Google route now sets no-store right after the same-site gate and
switches to private, max-age=300 only on a confirmed answer, so the
proxy's own 400, 405, 429 and 502 replies are no longer left without a
header. Both Places routes answer an unreadable 200 body with 502 instead
of caching an empty result, as the geocode routes already did. The test
pins the allowlist with OVER_DAILY_LIMIT and UNKNOWN_ERROR and covers the
unreadable and empty Places bodies; the changelog fragment is shorter.
This commit is contained in:
German Khokhlov committed 2026-11-19 18:29:24 +04:00
1 parent f22701ae70
commit 31b6b25d8b
4 files changed
+103 -35

No files matched your search

@@ -1,4 +1,2 @@
- Stop the browser caching a refused Google Places or Geocoding answer. The
proxies sent `private, max-age=300` on a 403 and on a geocode
`REQUEST_DENIED` or `OVER_QUERY_LIMIT`, so a fixed key kept failing for five
minutes; refusals are now `no-store` (Rudy Celekli, @rudycelekli, #1570).
- Stop the browser caching a refused Google Places or Geocoding answer, so a
fixed key works at once (Rudy Celekli, @rudycelekli, #1570).