Replies: 1 comment 2 replies
-
The time interval for a proxy can send/read packets successfully usually can measure the network quality between the proxy and the backend, so that's why the meanings of these two timeouts will care about the successive operations. The total time for a request/response cannot be decided easily as it's subjected to the size of request and response. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I found 3 timeout configs in apisix and in nginx:
I searched for a while but cannot find clear answer, so I want to ask there:
for connect_timeout. it's intuitive( TCP dial timeout). But what's send_timeout and read_timeout?
from nginx's doc, it means
the timeout between to successive send operatiosn
. And read_timeout meansthe timeout between to successive read operatiosn
. But it's pretty confusing! I mean why I need to care about timeout between two isolated I/O operations? I just care about how much time the proxy have to wait for the upstream to handle the request and reponse to proxy. And I want to know how to configure for that purposeBeta Was this translation helpful? Give feedback.
All reactions