You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "tokers (via GitHub)" <gi...@apache.org> on 2023/03/28 09:53:55 UTC

[GitHub] [apisix] tokers commented on issue #9122: bug: plugins.proxy-rewrite does not work with path size > 2

tokers commented on issue #9122:
URL: https://github.com/apache/apisix/issues/9122#issuecomment-1486554066

   > "GET /servicea/cookies/12 HTTP/1.1" 404 233 0.060 "-" "insomnia/2022.7.5" XXXXXXXXX "http://www.example.com/cookies/set/john/121"
   
   As you can, the last field is URL after the rewriting, which doesn't contain the `services` prefix. We believe the route was matched. So how did you judge the `404` is generated by Apache APISIX and is due to route not found?
   
   Addiontially, please use this URL to access your upstream directly and see if any error occurs. If you still think it's an APISIX error, try to open the flag `show_upstream_status_in_response_header` in `config-default.yaml`, which will show the upstream status in HTTP response headers.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org