In current Version 3.4.1 one can observe this behavior:
If the image-json-data got updated (i.e. via cronjob), the new image data doesn't show up in the browser. Apparently, its cached. I've notice that, when I was loading a brand new snapshot-build, but the date was still pointing out that this image would have been built a month ago. Disabling the cache in development tools fixed that immediately.
Expected Behaviour
It would be really great to have that caching somehow deactivated by default. Most users won't select that option in their browsers and would get displayed deprecated data then.
Problem Description
In current Version 3.4.1 one can observe this behavior: If the image-json-data got updated (i.e. via cronjob), the new image data doesn't show up in the browser. Apparently, its cached. I've notice that, when I was loading a brand new snapshot-build, but the date was still pointing out that this image would have been built a month ago. Disabling the cache in development tools fixed that immediately.
Expected Behaviour
It would be really great to have that caching somehow deactivated by default. Most users won't select that option in their browsers and would get displayed deprecated data then.