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
Net effect: a single xhr request timing out results in the connection going into the 'failed' state (so it won't be retried), which is suboptimal.
None of the individual steps seem obviously wrong. My stab at the least correct step is the last one: I'm not sure a failed transport should necessarily imply a failed connection. PR based on that: #135
The text was updated successfully, but these errors were encountered:
SimonWoolf
added
the
bug
Something isn't working. It's clear that this does need to be fixed.
label
Sep 25, 2015
An xhr request timing out (the sendTimeout) results in this chain of events:
Net effect: a single xhr request timing out results in the connection going into the 'failed' state (so it won't be retried), which is suboptimal.
None of the individual steps seem obviously wrong. My stab at the least correct step is the last one: I'm not sure a failed transport should necessarily imply a failed connection. PR based on that: #135
The text was updated successfully, but these errors were encountered: