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
After getting blocked, the RetryAfter as returned by fxa-customs-server and used to form the response header does not increase over time, which is bad for clients.
After the activity has been blocked, I'd expect the returned retryAfter to decrease, so that a client can tell the user how much longer to wait until the block is removed.
Actual result
The /check response always contains the initially reported number, even if the block is removed the next second.
Description
After getting blocked, the RetryAfter as returned by fxa-customs-server and used to form the response header does not increase over time, which is bad for clients.
Steps to reproduce
/check
route returns that the user is blocked, e.g.:/check
Expected result
After the activity has been blocked, I'd expect the returned
retryAfter
to decrease, so that a client can tell the user how much longer to wait until the block is removed.Actual result
The
/check
response always contains the initially reported number, even if the block is removed the next second.Environment
Not applicable
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: