31
Rate limits on postRest or graphql
Source: supabase/supabase#19493 · opened by @Jonatthu
How to configure or make rate-limiting decisions on each table or per action, with custom logic based on auth.jwt() or other things.
If I call from the frontend using anon key with or without JWT supabase.from('users').select('id, name') <-- What's the reate limits for this? How can I update the logic being used?
The only work around is to disallow anon and authenticated roles to use supabase queries on the frontend at all and set everything behind a edge functions and apply Upstash, but that does not seem what supabase is trying to achieve.
If I call from the frontend using anon key with or without JWT supabase.from('users').select('id, name') <-- What's the reate limits for this? How can I update the logic being used?
The only work around is to disallow anon and authenticated roles to use supabase queries on the frontend at all and set everything behind a edge functions and apply Upstash, but that does not seem what supabase is trying to achieve.
No pledges yet. Be the first to back this.
Comments
Similar requests
Auth Rate Limits by email address (or Supabase user ID) instead of by IP address
4 votes · 0 comments
Simple rate limiting for almost all services needed ?!
3 votes · 0 comments
Increase the batch size query for GraphQL (currently limited to 30 items)
1 vote · 0 comments
supabase Storage: custom rate limits
1 vote · 0 comments
Add rate-limiter at project level for client side requests like 120 request/min
1 vote · 0 comments
No comments yet.