
The new s3-proxy we have on fd.o is just a redirecting agent: it queries the policy and, if allowed, returns a URL with temporary credentials where the client can pull the real data from. This means that nginx would see /fdo-opa/mesa-rootfs/misc?key=foo and /fdo-opa/mesa-rootfs/misc?key=bar as distinct objects, not knowing that it could cache only on the base URL. Strip the query params from the nginx cache key so we can actually do caching. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34244>