search

greenlaw110 / greenscript

A tool help web developers manage javascript/css rendering, including minimize and dependence management
42 stars 24 forks source link

Bad content-type from cached resources with Chrome (304 not modified) #61

Closed tomparle closed 11 years ago

tomparle commented 11 years ago

Hi,

since Chrome v26 I experience a bug on my webapp with Greenscript especially when using a local Play! server. When I refresh a page or navigate in my webapp, all CSS resources with status "not modified" (HTTP code 304) are not properly received by Chrome. It is correctly loaded when forcing a hard-refresh (shift+F5) or disabling Greenscript.

After investigation, the CSS files that should be cached have the wrong content-type "text/plain" instead of "text/css" which seems to be a part of the problem, but I'm not sure where to fix that.

More info about this issue in Chrome: http://productforums.google.com/forum/#!topic/chrome/zID6uQQfKH8 Tom

greenlaw110 commented 11 years ago

The new version (greenscript 1.2.11b) is published at http://gelinsoft.com/play/repo/. See also https://gist.github.com/greenlaw110/2868365

tomparle commented 11 years ago

Thanks for the fix !