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
It would be nice to be able to distinguish these. Particularly, requests to a third party provider are failing and it would be good to distinguish whether the request actually made it to their server (their problem) or not (our problem).
It would also be neat because you could figure out whether or not the request made it to the server - a connection timeout is always retry-able, a read timeout on a POST is not.
The text was updated successfully, but these errors were encountered:
This request times out because the
connect
socket call fails:This request times out because the
read
socket call doesn't see any response in 3 seconds:(I'm using hamms in the second test)
It would be nice to be able to distinguish these. Particularly, requests to a third party provider are failing and it would be good to distinguish whether the request actually made it to their server (their problem) or not (our problem).
It would also be neat because you could figure out whether or not the request made it to the server - a connection timeout is always retry-able, a read timeout on a POST is not.
The text was updated successfully, but these errors were encountered: