-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Response caching issue #3350
Comments
@codingjoe thanks for reporting. Is it possible to have strip things and have a minimum test case for this specific issue ? |
We do have unit tests for response caching. Django master has a response issue that's resolved in the 3.3 branch, which we plan to have that merged in prior to 1.9. In the absence of any actually helpful minimal reproducible case, I'm going to assume that running against Django master is the issue. If that's not the case and you still believe there's an issue then I'd appreciate a little more work on narrowing down a minimal reproducible case, so that we can help. |
I'm seeing this issue as well and I think I can add a bit more clarity. It appears that the
|
Think it needs reopening then? |
A new issue that |
Gotcha |
Pickel do not work since version 3.2.* on a restframework response. Thus caching responses doesn't work if you use the pickel serializer for caching.
The text was updated successfully, but these errors were encountered: