Static resources need Expires headers

[marians]

Once we're in production, all static resources should be transferred with Expires-headers that allow for caching for at least 24 hours.

Currently, for the home page about 2,2 MB of files are transferred. When changing to save and detail view, the heavy json files and JavaScript, which have already been loaded, are loaded again. This should be avoided.

[marians]

Actually expires headers are set, along with a lot of other cache-influencing headers.

As an example, here are the response headers for a css file:

Cache-Control: public, max-age=43200
Connection: keep-alive
Content-Length: 81443
Content-Type: text/css; charset=utf-8
Date: Sat, 28 Apr 2012 22:37:56 GMT
ETag: "flask-1335630896.86-81443-1985555092"
Expires: Sun, 29 Apr 2012 10:37:56 GMT
Last-Modified: Sat, 28 Apr 2012 16:34:56 GMT
Server: nginx/0.7.65
Set-Cookie: session="IZK844h3a4CHUU02CIjgyc08RHM=?lang=Vml0CnAxCi4="; Path=/; HttpOnly

It just seems as if Chrome either ignores this or it fools me in the network console.