The STK's javascript loader libraries define by their modification date the time stamp in the far future caching strategy -> the url output of the resource.

This means when a resource, any JS for example, gets changed, the time stamp will remain the same because the scrip-loaders didn't change at all. The will still have the same modification date.

Possible solution:
Newest modification date of all resources is used.

Becuase there are many modulees involved, resources & STK & cache, I created this issue to main Magnolia project.

Also the Url pattern could be optimized. Long ago Aperto wrote a mail to Philipp, explaining problems they have with this URL pattern based on Apache rewrites and VirtualURIMappings.