Forum Discussion
CirrusF5 XC HTTP 404 rout_not_found / rsp_code 404
I would like to add more point about the HTTP 404 error: route_not_found / rsp_code 404 in an XC (RE + CE) deployment.
1. Even if XC has the correct host match value in the route, you might still observe a 404 response. In such cases, check the DNS configuration on the CEs.
A possible reason could be that the CEs are unable to resolve DNS for host which is configured in route.
2. Even if XC has the correct host match value, the path might not match. For example, if you have a single route as shown below and the request comes as https://example.com/, you may see rsp_code 404 , as it is not matching any routes.
Example :
HTTP Method:ANY
Path Match : Prefix
Prefix:/hello
Headers
Host example.com
Orginpool: example_orgin pool
2 Replies
Karthick1Below are the response
Request & Response
req_id
XXXXXXXXXXXXXXXXXXX0
method GET
host example.com
req_path/
req_body -
api_endpoint :UNKNOWN
scheme :https
rsp_code :404
rsp_code_details :route_not_found- Nikoolayy1
MVP
The XC CE does not resolve the host in the route match. Maybe you mean can't resolve the pool's origin server that route uses. If the pool under the route is FQDN and the CE or RE can't resolve it then you can get similar error or "cluster_not_found" in the logs.
For the second point yes this is why have a default pool under the HTTP LB or default route at the end with Prefix:/
Also for HTTPS you may get RST (I think on the RE) in some cases and the logs will show the clear error.
