When configuring resource resolution with versioning support (especially custom content versioning implementations), it appears that in rare cases there can be a collision in the URL path like so: "/static/images-c0ff33/image-c0ff33.png". The current implementation fails because the resolver attempts to locate "/static/images/image.png" instead of "/static/images-c0ff33/image.png"

This situation is quite rare, but content versioning should only consider the last instance of the version string because the hash is calculated with the resource content.