mirror of
https://github.com/ipnet-mesh/meshcore-hub.git
synced 2026-06-26 04:51:59 +02:00
Louis King
fd55968b39
The SPA reaches the backend via the web api_proxy, which forwarded query params using dict(request.query_params). dict() on Starlette's QueryParams multidict keeps only the last value of a repeated key, so a multi-valued filter like ?observed_by=A&observed_by=B was forwarded to the backend as observed_by=B only. The backend then filtered to B's events, making a message observed only by A disappear as soon as B was also selected — the reported "filters act like AND" symptom. This happens independently of the Redis response cache. Forward request.query_params.multi_items() (a list of (key, value) tuples) so all repeated values reach the backend. Add web proxy regression tests asserting both observed_by values are forwarded, and capture forwarded params in the MockHttpClient. This is the primary fix; the earlier cache-key change (multi_items in sorted_query_string) addressed the same collapse pattern at the cache layer. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>