I think I discovered a bug on serving changed and cached files. I tried with .css and .less ones.
- The first time is asked a content, everything is ok
- The second time, file is served from cache and everything is still ok
- After file changes, served file is changed, but his content length is the same as the first cached version
This causes trunk files or extra chars at the request end, depending of length diffs.
Before to test, I patched content-type issue, as described here: http://java.net/jira/browse/GRIZZLY-1014