We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
apache/apisix#10620
Sorry, something went wrong.
The bug is caused by differences between OpenResty and Nginx.
In Nginx's ngx_http_upstream.c:
ngx_http_upstream.c
if (!u->request_body_sent) { u->request_body_sent = 1; if (u->header_sent) { return; } ngx_add_timer(c->read, u->conf->read_timeout); if (c->read->ready) { ngx_http_upstream_process_header(r, u); return; } }
The added read_timeout is u->conf->read_timeout.
read_timeout
u->conf->read_timeout
However, in OpenResty, due to the HAVE_NGX_UPSTREAM_TIMEOUT_FIELDS macro, OpenResty directly uses u->read_timeout.
HAVE_NGX_UPSTREAM_TIMEOUT_FIELDS
u->read_timeout
But the ngx_multi_upstream_module does not account for this difference.
ngx_multi_upstream_module
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: