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 <[email protected]> wrote:

Hi,

currently I'm a bit clueless. When I use for example: [[image:XWikiLogo.png||width="50" height="50"]] the image is only resized with the attribute style but not transfered resized. When I inspect the image via chrome the "natural size" is still the original size.

The html result: </xwiki/wiki/example.com/download/Sandbox/WebHome/XWikiLogo.png?width=50&height=50>

We are using XWiki 4.4 (XEM) The document is saved with XWiki Syntax 2.1 (I tried 2.0 also) in the xwiki.properties I set explicitly rendering.imageDimensionsIncludedInImageURL = true (but this should be the default)

Is there a wiki wise way to override the behaviour incidentally?

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:

Hi there,

I just updated XWiki from 4.4 to 4.4.1 and it's now perfect.

For others run in this problem: If you updated double check the browser caching, it wasn't done with shift + f5 in chrome.

Thanks a lot for the answer