-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
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
help request: 499 error code!!!help!!! #7121
Comments
Are there any steps to reproduce? With only these simple descriptions, no one can know what happened |
For example: It happened! |
For example: It happened! |
see: #4715 |
I've tried. It doesn't work. |
Go to 400 error. |
In any case, the information you gave is not enough for me to reproduce the error you encountered. I need
For all of the above information, text is required rather than screenshots. If you don't know how to prepare this information, you can refer to these issues for how to provide effective information. |
thanks |
499返回码一般是客户端主动超时产生的错误呀,是不是客户端默认加了60S的timeout?
所以你现在的问题是APISIX超时无法突破60s么?
来调整超时设置。 |
这些我都尝试了都不行,对于我来讲,如果让我解决这个问题,我只能去看源码的流程,看是否哪里写死了60s;不过我对lua语言不熟,所以没有这么做。 |
是不是这样: 那APISIX的日志显示的返回码是多少呢? 还有个笨办法,你弄个nginx代理,代理到上游试试呢? |
我最近直接请求apisix的管理端api(如域名/apisix/admin/routes)这种接口,也偶尔报499,好奇怪 |
@StretchV Could you check out if the communication between APISIX and ETCD is slow? 499 means the client closes the connection before server-side returning any byte. |
Problem solved,It turns out that the upstream of this route is unstable |
Problem solved,it is version problem,change newlest version,it's ok! |
Description
I need to request a time-consuming operation through apisix, which will take more than 60 seconds.Both postman and curl return errors, unless you don't use apisix. I tried almost all the settings about keepalive, but it didn't work. 400 error code returned when modifying 'proxy_ignore_client_abort on'.
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: