id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	parents
266	Improve cache friendliness of static content	Elrond	Christopher Allan Webber	"{{{
#!rst
If not serving the (semi-)static content (css etc and the media
items) through a dedicated webserver but using paste#static the
caching is bad.

It could easily be argued, that on a real deployment, these tings
should be served by a dedicated webserver. But still, the paste
based setups should give reasonable caching.

There are two items to consider:


1. mediagoblin/mgoblin\_static/ (CSS, ...)

Only layout/etc developers will change this and those will likely
use ""reload"" on their browsers anyway. Everybody else will only
change this when updating their install. So even thinking about
people updating and wanting a fresh look soon, at least an hour
would be good. I'd rather suggest a day.


2. media content (public\_store)

media items aren't **modified** currently. They get written once
and stay there as written. Creating a new media entry, creates a
new object id, etc. I'd say a week is good.



}}}"	defect	closed	minor	0.1.0	programming	FIXED