Set caching headers in dynamic resizer

Bug #887352 reported by François Marier on 2011-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libravatar
Medium
Unassigned

Bug Description

Currently the 307 redirects to the dynamic resizer are not cached at all.

Both the output (coming from Django) of the resizer should be cached, but also the 307 redirect itself on the CDN.

The image output should probably be cached for 1 hour whereas the 307 redirect should be cached for 5 minutes.

Changed in libravatar:
assignee: François Marier (fmarier) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers