http://www.muhuk.com/2009/05/serving-static-media-in-django-development-server/?utm_source=rss&utm_medium=rss&utm_campaign=serving-static-media-in-django-development-server know thyself Thu, 29 Dec 2011 08:49:39 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.muhuk.com/2009/05/serving-static-media-in-django-development-server/comment-page-1/#comment-236 Can Mon, 25 May 2009 19:32:28 +0000 http://www.muhuk.com/?p=225#comment-236 <p>what you need is to keep track of md5's of all static files in memory, then generate false paths for each static file such as /dres/34AEFAA1785DDD/file.css - then use url redirecting to direct /dres/[regexp]/*.css to actual path. then you can use a filter to rewrite the http response header in such a way that every file you serve has a long expiry date like 10 years. This way you never send the same file to the same client again, yet when the file changes the checksum changes, and the client cache is therefore flushed. You need to be able to masterfully modify the http header (multiple fields - expires, pragme and cache-control) with your own values. Too much fuss just to serve files? Thats the way you do it.</p> what you need is to keep track of md5′s of all static files in memory, then generate false paths for each static file such as /dres/34AEFAA1785DDD/file.css – then use url redirecting to direct /dres/[regexp]/*.css to actual path. then you can use a filter to rewrite the http response header in such a way that every file you serve has a long expiry date like 10 years. This way you never send the same file to the same client again, yet when the file changes the checksum changes, and the client cache is therefore flushed. You need to be able to masterfully modify the http header (multiple fields – expires, pragme and cache-control) with your own values. Too much fuss just to serve files? Thats the way you do it.

]]>