Sounds like an SRE prioritizing middlebox cacheability over developer UX. Something like: "Public-readable resources get requested a lot, with no predictabilit

Sounds like an SRE prioritizing middlebox cacheability over developer UX. Something like: "Public-readable resources get requested a lot, with no predictability over who or how many independent agents could be requesting them at once; so, to decrease the likelihood of requests on such resources DDoSing our backend, we could at least limit there to being exactly one canonical way to acceptably request the URLs of such resources. That way, such resources will end up hot in any edge-cache after the first request, and any non-normalized requests will break [and so be removed from the logic] — rather us needing to serve the same resource multiple times to get it saved under under multiple cache keys." (I'm guessing that S3 also errors out if you submit random unrecognized query-string parameters on such requests?)