controller caching fails CRUD endpoints for subsequent calls #176
Comments
peterstadler
added a commit
that referenced
this issue
Nov 15, 2023
The caching was blocking further requests for different HTTP methods. So, once an e.g. OPTIONS request was cached with a 404, subsequent calls to the same endpoint but via GET where hitting the 404 as well
peterstadler
added a commit
that referenced
this issue
Nov 16, 2023
The caching was blocking further requests for different HTTP methods. So, once an e.g. OPTIONS request was cached with a 404, subsequent calls to the same endpoint but via GET where hitting the 404 as well
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When calling (via GET) e.g.
http://localhost:8080/data/read?filename=incipit_demo.xmlAND providing an Accept header ('application/json' or 'application/xml') the endpoint returns the requested XML file. However, after doing an OPTIONS request, this same call returns 404.steps to reproduce
curl -i -H "Accept: application/xml" "http://localhost:8080/data/read?filename=nielsen_cnw0131.xml"returns 200curl -I "http://localhost:8080/data/read?filename=nielsen_cnw0131.xml"returns 404curl -i -H "Accept: application/xml" "http://localhost:8080/data/read?filename=nielsen_cnw0131.xml"returns 404(!)The text was updated successfully, but these errors were encountered: