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
Retry middleware implements retry based on timeout.
But when timeout happens prev request can still be in fly and consume resources. I.e. prev request is not stopped/canceled.
Browsers limit number of concurrent requests. And default timeout for fetch varies in different browsers and can be 2-3 minutes.
Since we are not going to wait for prev request to be finished should we cancel/stop it?
The text was updated successfully, but these errors were encountered:
Retry middleware implements retry based on timeout.
But when timeout happens prev request can still be in fly and consume resources. I.e. prev request is not stopped/canceled.
Browsers limit number of concurrent requests. And default timeout for
fetch
varies in different browsers and can be 2-3 minutes.Since we are not going to wait for prev request to be finished should we cancel/stop it?
The text was updated successfully, but these errors were encountered: