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
Given the single-user use-case, we don't have to care much about rate limiting authenticated requests (we can assume the authed user is trustworthy)
But, for any unauthed endpoints, particularly those that trigger outbound traffic (e.g. appview forwarding), we should be careful not to allow spammy requests.
If the AppView ratelimits us, for most cases we're probably fine to forward its response (including rate limit headers) back to the client.
The text was updated successfully, but these errors were encountered:
Given the single-user use-case, we don't have to care much about rate limiting authenticated requests (we can assume the authed user is trustworthy)
But, for any unauthed endpoints, particularly those that trigger outbound traffic (e.g. appview forwarding), we should be careful not to allow spammy requests.
If the AppView ratelimits us, for most cases we're probably fine to forward its response (including rate limit headers) back to the client.
The text was updated successfully, but these errors were encountered: