CCTV Street View budget: key the client before the camera wait, share the default

- The /frame handler reads the client's network key (IPv6 /64) before it
  awaits the camera, so a client that drops the connection is still
  charged to its own window instead of the shared fallback key.
- The budget is charged only after the Google key and finite catalog
  coordinates are confirmed, and the key is read once.
- Places and the CCTV window share one default (GOOGLE_DEFAULT_PER_MIN).
- Tests: the catalog-only test checks heading/fov/pitch from the query at
  the catalog location; the budget test covers unknown ids, forwarded
  requests and /64 grouping; a real-socket test covers a dropped
  connection. The duplicate pose test is removed.
- .env.example, SECURITY.md, CURRENT-STATE and the changelog fragment
  describe the separate per-IP window, the catalog position and the
  placeholder for seed cameras.
This commit is contained in:
German Khokhlov committed 2026-11-20 11:31:14 +04:00
1 parent 01368b95bf
commit 01d4a3f454
10 files changed
+175 -201

No files matched your search

@@ -1,5 +1,5 @@
- The CCTV Street View fallback serves only catalog cameras, always at their
catalog position, and ignores coordinates a request supplies. It has its own
per-client limit on the Google setting (`GEV_RATELIMIT_GOOGLE_PER_MIN`,
default 120), so the Google key can no longer be used as an unmetered Street
View service (asturksever, #1602).
- The CCTV Street View fallback answers only for cameras the server lists, at
their catalog position; a request sets only the view. Bundled seed cameras
get the placeholder. A per-IP limit on `GEV_RATELIMIT_GOOGLE_PER_MIN`
(default 120) keeps the Google key from serving as an unmetered Street View
service (asturksever, #1602).