You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zarr.nemar.org rate-limit bypass (backend/src/index.ts:225): the zarr.nemar.org host returns zarrDataRoutes.fetch() directly, bypassing the API middleware stack (and its rate limiter), unlike data.nemar.org which re-enters api.fetch(). It is the highest-request-volume path. (Note: it does have edge caching via caches.default, so this is rate-limiting only.) Apply the data-plane rate-limit bucket to the zarr host path.
STS s3:ListBucket over-scoping (backend/src/services/sts.ts): per-session federation tokens grant unconditional s3:ListBucket on the bare bucket (no s3:prefix condition), because git-annex initremote's HeadBucket can't be prefix-scoped. Consequence: any user requesting credentials for their own dataset can enumerate object keys of every other dataset, including private/embargoed. Scope the per-session policy by prefix and move the HeadBucket bootstrap to a separate narrow path.
Activity
Address #901 review: /zarrproxy bucket + 429 CORS
Phase 6: rate-limit the zarr data plane (#901) (#942)
neuromechanist commentedon Jul 7, 2026
zarr rate-limit half shipped in epic #896 (dev via #943). STS ListBucket prefix-scoping split to #941 (needs live git-annex validation).