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
Is your feature request related to a problem? Please describe.
src/server/app.js has limits on the rate of certain types of requests but the OED user is not notified when the request fails for this reason.
Describe the solution you'd like
It would be nice to notify user if limit is hit and maybe to retry after a given delay. Care should be taken that the retry does not enter a bad loop as many are retried.
Describe alternatives you've considered
Leave as is
Additional context
Normally the rate limit is only hit by malicious use or coding/scripting errors. Thus, OED does not expect the limit to be hit (may happen rarely) for regular usage. Normally a retry would fix this.
The text was updated successfully, but these errors were encountered:
PR #1370 added messages when you hit the rate limit but doesn't always display.
This fix only applies to cases where the user hits a limit on the main page but not a subroute.
Is your feature request related to a problem? Please describe.
src/server/app.js has limits on the rate of certain types of requests but the OED user is not notified when the request fails for this reason.
Describe the solution you'd like
It would be nice to notify user if limit is hit and maybe to retry after a given delay. Care should be taken that the retry does not enter a bad loop as many are retried.
Describe alternatives you've considered
Leave as is
Additional context
Normally the rate limit is only hit by malicious use or coding/scripting errors. Thus, OED does not expect the limit to be hit (may happen rarely) for regular usage. Normally a retry would fix this.
The text was updated successfully, but these errors were encountered: