3
Rate limiting for Storage and Image Transformations API calls
Source: supabase/supabase#29108 · opened by @arbyruns
Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: • Docs: • Discussions: • Discord: Before opening a bug report, please verify the following: --> • I confirm this is a bug with Supabase, not with my own application. • I confirm I have searched the [Docs]( GitHub [Discussions]( and [Discord]( Describe the bug Currently, there is no ability to disable storage image transformations and if a user is able to determine where images resides can make repeated image transformation calls. An unknown actor can then make repeated calls churning through usage. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Have images reside in storage and send a transofrmation API call. 2. An example of the URL being sent to my project Expected behavior Ability to disable this feat…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add support for image transformations in bulk storage URL signing (getSignedUrls)
2 votes · 0 comments
Simple rate limiting for almost all services needed ?!
3 votes · 0 comments
SMS rate limiting requests/feedback
2 votes · 0 comments
Auth Rate Limits by email address (or Supabase user ID) instead of by IP address
4 votes · 0 comments
Add Storage Adapter For Chrome.Local.Storage Api
3 votes · 0 comments
No comments yet.