Skip to content

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

Closed
wangfeng22 opened this issue Nov 8, 2022 · 8 comments
Closed

Comments

@wangfeng22
Copy link

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 (run apisix version): 2.13.2
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@monkeyDluffy6017
Copy link
Contributor

Could you provide a minimal reproduction use case with detailed steps?

@tzssangglass
Copy link
Member

maybe fix by: #7466 and release in v2.15.0

@wangfeng22
Copy link
Author

wangfeng22 commented Nov 9, 2022

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

@wangfeng22
Copy link
Author

wangfeng22 commented Nov 9, 2022

Could you provide a minimal reproduction use case with detailed steps?

  1. add several routes like routerA, routerB, routerC, and so on. The router support HTTP and HTTPS. The upstream is configured like http://domain.
  2. add routerD. Then a strange thing happened, routerD occasionally returns 404 page not found. In fact, the upstream of routerD don't handle the 404 requests.

I don't know what returns 404 page not found. routerA, routerB and routerC are working well. I have restarted apisix, but this problem still exists. @monkeyDluffy6017

@wangfeng22
Copy link
Author

wangfeng22 commented Nov 9, 2022

maybe fix by: #7466 and release in v2.15.0

image

The 404 response is returned right now, and it doesn't get a response from upstream. You can see it from No number.
@tzssangglass

@wangfeng22
Copy link
Author

wangfeng22 commented Nov 9, 2022

@tokers Could you help me see see? Looking forward to your reply.

@tzssangglass
Copy link
Member

The 404 response is returned right now, and it doesn't get a response from upstream. You can see it from No number.

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?

@wangfeng22
Copy link
Author

wangfeng22 commented Nov 9, 2022

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

@apache apache locked and limited conversation to collaborators Nov 9, 2022
@tzssangglass tzssangglass converted this issue into discussion #8288 Nov 9, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants