Hi, There was a bug on 4.4, which is fixed in 4.4.1: http://jira.xwiki.org/browse/XWIKI-8663 Thanks -Vincent On Jan 26, 2013, at 8:02 AM, Jan-Philip Loos <maxdaten(a)gmail.com> wrote:

Jan-Philip, my experience there is that browser caching is acting differently depending wether it's a "top-level" resource or an included resource. Images are typically never top-level resources (they are embedded in html pages) but you can open them in a separate tab using a contextual menu command. Reloading then can only mean actually fetching the image from the server. This changes the cache entry; following html pages can then use the properly refreshed cache entry. The same applies when you change included js or css files although browsers have a tendency to look somewhat randomly at refreshing their cache, leveraging the if-modified-since header quite a lot. There seems to be some black-art hidden there which is likely related to some statistical profiles of each server (e.g. a server which changes frequently would be more refetched)... Paul On 26 janv. 2013, at 23:40, Jan-Philip Loos wrote: