#27572 closed Cleanup/optimization (wontfix)

Static files served in development should prevent caching

Reported by: Kevin Christopher Henry Owned by: nobody
Component: contrib.staticfiles Version: 1.10
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Currently, when Django serves static files in development with runserver and django.contrib.staticfiles it doesn't provide any cache headers. In their absence, user agents are free to cache the resources however they like. That means that when the developer updates a static resource they can't predict whether or not they will see the new version or the older cached version.

Dealing with this on the user agent side isn't always easy. For example, if you're using an embedded browser in a native app you'll probably have to create a remote debugging connection to the app and use platform-specific development tools to manipulate or disable the cache.

Since caching is a performance optimization that makes development more difficult and less predictable, I think it makes sense to disable it (via the appropriate HTTP headers) for static resources served in development.

Change History (3)

comment:1 Changed 22 months ago by Tim Graham

We've been thinking about replacing our own staticfile serving code with something like whitenoise (#27572). Do you know if it has a suitable option?

Last edited 22 months ago by Tim Graham (previous) (diff)

comment:2 Changed 22 months ago by Kevin Christopher Henry

I haven't used whitenoise before, but based on the documentation it looks like it's already doing what I proposed above:

WHITENOISE_MAX_AGE
    Default: 60 if not settings.DEBUG else 0

Time (in seconds) for which browsers and proxies should cache non-versioned files.

So, yes, a switch to whitenoise should solve this problem! I don't know how imminent that is, so I'll leave it up to you whether this is worth fixing in the meantime.

comment:3 Changed 22 months ago by Tim Graham

Resolution: wontfix
Status: newclosed

Great, I don't see much value in duplicating work then.

Note: See TracTickets for help on using tickets.
Back to Top