1
Native rate limiting for client-side SELECT requests to prevent egress abuse
Source: supabase/supabase#44131 · opened by @ericzager0
I have a Next.js SaaS on Vercel that communicates directly from the browser with Supabase, secured with RLS. My concern is that a malicious authenticated user could script millions of SELECT calls from the browser console and generate huge egress costs. Is there any native Supabase mechanism to prevent this without routing requests through a server-side proxy?
No pledges yet. Be the first to back this.
Comments
Similar requests
SMS rate limiting requests/feedback
2 votes · 0 comments
Simple rate limiting for almost all services needed ?!
3 votes · 0 comments
Compress text API responses before leaving data centre
2 votes · 0 comments
Auth Rate Limits by email address (or Supabase user ID) instead of by IP address
4 votes · 0 comments
TOTP Enrollment "Do not include QR" flag
1 vote · 0 comments
No comments yet.