-
Notifications
You must be signed in to change notification settings - Fork 2.5k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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: The route occasionally returns a 404 page not found #8280
Comments
Could you provide a minimal reproduction use case with detailed steps? |
maybe fix by: #7466 and release in v2.15.0 |
I have studied this issue for many days, and I find it difficult to understand the explanation of this problem. Why can't I restart Apisix to solve this problem. @tzssangglass |
I don't know what returns |
The 404 response is returned right now, and it doesn't get a response from upstream. You can see it from No number. |
@tokers Could you help me see see? Looking forward to your reply. |
Are you saying that this problem still exists in 2.15.0? Or are you insisting on reproducing and working on this issue on 2.13.2? |
I insist on reproducing and working on this issue on 2.13.2. I really want to know why this happened. This problem can be reproduced in the case of pressure measurement. It is difficult to understand the explanation of this problem in this issue #7466 @tzssangglass |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Description
I have configured several routes, and everything going well. But when I added a new route, sometimes this route returned 404 page not found. That's really abnormal.In fact, the back-end didn't handle the 404 requests.
I have restarted apisix, but this problem still exists. Only the domain name added later has this problem.
ps: The Route support http and https. The Upstream is configured like http://
domain
Environment
apisix version
): 2.13.2uname -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: