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
We have a 1000ms timeout on socket and then these...
send: 10000,
response: 10000
I am struggling to properly understand what the socket step means.
"...socket starts when the socket is connected. See [request.setTimeout]..."
We are successfully sending the request to the server and the server is definitely actioning the request, though we are NOT receiving the server's response, however the timeout is not a response timeout it is a socket timeout.
I don't fully understand when the socket timeout ends and what that means and if the issue is likely to be client side (something our OS layer is not doing) or server side (something the server is not doing even though it receives and actions the request and we are not getting a response timeout per se).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have a 1000ms timeout on socket and then these...
send: 10000,
response: 10000
I am struggling to properly understand what the socket step means.
"...socket starts when the socket is connected. See [request.setTimeout]..."
We are successfully sending the request to the server and the server is definitely actioning the request, though we are NOT receiving the server's response, however the timeout is not a response timeout it is a socket timeout.
I don't fully understand when the socket timeout ends and what that means and if the issue is likely to be client side (something our OS layer is not doing) or server side (something the server is not doing even though it receives and actions the request and we are not getting a response timeout per se).
Many thanks
Beta Was this translation helpful? Give feedback.
All reactions