-
Notifications
You must be signed in to change notification settings - Fork 202
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
Browser not caching generated images (no 304) #20
Comments
Good point, as you can see here Glide currently does not set a 304 response code. However, you're absolutely right, it should. Leave it with me! |
oh.. well that explains it - been trying to figured what I hadn't done. Will leave it with you then. Thanks. |
Just a note here. It appears that a 304 should only be returned in the event that the browser sends a |
This is done and will be included in the 0.3.0 release. |
The browser is not caching images generated by Glde.
The images are returned fine - but subsequent requests should return a
304
, correct?I'm getting
200
's every time.I'm caching in Redis (also tried the file system).
Any ideas on why this would be?
Request:
Request headers:
Response headers
Action method:
The text was updated successfully, but these errors were encountered: