#29277: Add a bust_browser_cache flag to the static template tag
-------------------------------------+-------------------------------------
Reporter: David Kerkeslager | Owner: nobody
Type: New feature | Status: new
Component: Template system | Version: 2.0
Severity: Normal | Resolution:
Keywords: browser-cache- | Triage Stage:
busting static-files | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David Kerkeslager):
Replying to [comment:2 Simon Charette]:
> Isn't this something that is already implemented through
`ManifestStaticFilesStorage` and `CachedStaticFilesStorage`?
>
>
https://docs.djangoproject.com/en/2.0/ref/contrib/staticfiles/#manifeststaticfilesstorage
Hm. I wasn't aware of that and it is pretty similar, but doing that
globally and continuing to store the old files means that a) we can't turn
it on/off for individual files (i.e. the hash time for videos/images
probably isn't worth it, as they don't change as much as CSS files) and b)
references to old files don't throw any errors, they just fail silently. I
think that will handle my use case, though. Thanks for taking the time to
respond.
--
Ticket URL: <https://code.djangoproject.com/ticket/29277#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.4f2f60cfffcd938a3b324b0f716b2699%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
