Chrome (32) does not cache all-in-one files.

[lewisgoddard]

This seems to be an issue with chrome, which is setting the Cache-Control to max-age=0 and ignoring the response. I'm not entirely sure how you would go about fixing this, maybe by appending script.js to the end of the URLs so it expects JavaScript (it seems unsure about what to expect).

Request

Request URL: http://cdn.jsdelivr.net/g/modernizr,selectivizr,jquery,jquery.equalize
Request Method: GET
Status Code: 200 OK

Request Headers

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-GB,en;q=0.8,en-US;q=0.6
Cache-Control: max-age=0
Connection: keep-alive
Host: cdn.jsdelivr.net
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36

Response Headers

Access-Control-Allow-Origin: *
Cache-Control: public, max-age=315360
Connection: keep-alive
Content-Encoding: gzip
Content-Type: application/javascript
Date: Sun, 16 Feb 2014 13:23:29 GMT
Server: nginx
Transfer-Encoding: chunked
Vary: Accept-Encoding
X-Age: 2199
X-Cache: HIT
X-Cache: HIT
X-Edge-IP: 185.2.138.117
X-Edge-Location: London, GB

[jimaek]

It doesnt look like an issue at all

http://superuser.com/questions/313131/how-do-i-stop-chrome-sending-cache-control-max-age-0-when-i-hit-enter

[lewisgoddard]

Okay, so apparently this only happens because I am refreshing. I had no idea that effectively bypassed the cache, it seems like an odd move. As I said, I assumed it was something to do with type checking, but it does seem fine when loaded through a link.