Revolyssup commented on issue #9688:
URL: https://github.com/apache/apisix/issues/9688#issuecomment-1605312747

   1. The only place where the annotation `http-allow-methods` is used inside 
ingress-controller is here - 
https://github.com/apache/apisix-ingress-controller/blob/32c07516b6bf2fe8ff86ecdf65ee04a7afc0c535/pkg/providers/ingress/translation/annotations/plugins/http_method.go#L41,
 which is configuring response-rewrite plugin. Also to clarify, the parameters 
passed in the annotation `http-allow-methods` do not correspond to the 
`methods` field passed in route configuration. 
   
   2. I cannot reproduce this issue on either memory or disk. Following this 
https://apisix.apache.org/docs/apisix/plugins/proxy-cache/, I create a route 
and perform PURGE resulting in 404. Then I do GET and it succeeds.  The only 
place where proxy-cache returns 404 from APISIX's end is on PURGE. Otherwise 
the statuscode is what's returned from upstream. And since in case of PURGE, no 
state change takes place, this shouldn't be an issue. I am still looking into 
it. Meanwhile Can you show the response headers on the subsequent GET requests 
which are returning 404? @namdiag 
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to