-
-
Notifications
You must be signed in to change notification settings - Fork 521
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
PATCH returns cached response #407
Comments
Hello, Indeed I got the same issue, when update or delete the code get the resource first, then update or delete it and get the resource again. The cache should only be use for HTTP GET method. I created a PR to solve the issue. |
This was referenced Apr 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like GET requests are cached, so when performing a PATCH request, it modifies the db row, but then returns the result from cache.
PUT
seems to not be affected by this issue.The text was updated successfully, but these errors were encountered: