I have created this issue in Mangolia-UI because its a specific behavior one has only when rendering a page trough the admin central in combination of magnolia.develop=false

Of course Cache and Imaging and Assets app is also involved.

Problem

Authors won't see image changes in pages app on a production environment ('magnolia.develop=false')

Description:

As base has to be set: 'magnolia.develop=false'

Accessing a page trough pages app that contains an image.
When cropping the image in Assets app, the page rendered within the pages app does display the old image. It takes 10 minutes until the cropped image is displayed (seems this cache config kicks in: 
/modules/cache/config/contentCaching/defaultPageCache/browserCachePolicy/policies/default

One can verify by clearing the browser cache and the new image is shown.

When accessing the image NOT trough AdminCentral (never rendered the page in pages app!!) the image reacts instantly every time it gets changed!

It doesn't matter whether the image is served via '.imaging' servlet or via '/dam/' servlet.

Reproduce:

1. set: 'magnolia.develop=false'
2. Render in pages app a page containing an image
3. Crop the same image
4. Render the same page again in pages app -> image doesn't change
5. Access the image via its url, still browser cached & doesn't change.
6. Clear browser cache (or wait 10minutes  ) and see, the images changes

Proof its admin central:

• set: 'magnolia.develop=false'
• Render in a page containing an image via its direct URL
• Crop the same image
• Render the same page again via its direct URL -> image does change
• Access the image via its url > image does change