DAM Asset's Renditions break asset in Dispatcher cache
The problem is that say you have a video asset in the DAM, http://mysite.com/content/dam/mysite/resources/videos/Patient-Centered-Approach.mp4
I am using an HTML5 video player (jwplayer). It has two properties, the video file url and the url of the "poster" (“rendition” or “thumbnail”) image. The rendition technically is stored as a child node of the video in the JCR repository. So the full url to the rendition is:
The problem is that “Patient-Centered-Approach.mp4” cannot be both a file and a folder in the dispatcher cache at the same time, so if the image is requested first then the dispatcher will create a folder named “Patient-Centered-Approach.mp4” with a sub-folder named “jcr:content” down to the PNG image.
If the video is requested before the PNG then the video works, but the PNG will not (because “Patient-Centered-Approach.mp4” is a file in the cache not a folder).
This cannot be an unusual scenario. How is this usually handled?