Currently, the file extension implementation in the CMP seems inconsistently implemented.
The urls generated by the CMP do not contain a file extension.
https://images4.cmp.optimizely.com/assets/image001-12808-.png/Zz1jYzM4MmY1NjEzZDAxMWVmOTMzODZlM2ZmODAwZTZjYg==
The .png does not function as a file extension for the browser.
In the CMP, if I change the Title of an image, and leave the extension off, I get a warning, but it will let me do it. If I remove that extentsion, I end up with the url:
https://images4.cmp.optimizely.com/assets/image001-12808-/Zz1jYzM4MmY1NjEzZDAxMWVmOTMzODZlM2ZmODAwZTZjYg==
In both cases above, the header contains the correct file type, regardless of the url.
Normally for a physical file, something that can be downloaded to your local machine, I would expect the url to contain a file extension so that the local machine knows what kind of file it is. In the examples above, when I try to download, it uses the hash as the file name, and I assume it gets the file type from the header because it can determine the file type regardless of the url.
A more consistent and logical method for handling file types would be better for the front end user. If the CMP is going to throw an error if I try and change the file type, then I would expect a more consistent file type experience.
