3 ms·
> For example, a JPEG image at https://example.com/picture.jpg https://example.com/picture.jpg that has been converted to WebP will still have that same URL. Th
by philo23 10y ago
> For example, a JPEG image at https://example.com/picture.jpg https://example.com/picture.jpg that has been converted to WebP will still have that same URL. The “Content-Type” HTTP header tells the browser the true format of an image.
So if a visitor tries to download one of those images, are they going to end up saving the image with an incorrect file extension, or is it up to browsers to fix the file extension based off of the Content-Type header?
- jblok 10y agoIt will have the wrong file extension, but the bigger problem is that when the user tries to open the file in Preview on OSX or whatever their native picture viewing application is, chances are it will fail to open a WebP image. I recall Facebook experimenting with WebP, but abandoned it because when users saved images from the web to their hard drives, they couldn't work out how to open the files.
- niftich 10y agoIndeed Facebook tried this in 2013, and the user misery was immediate and loud [1][2]. [1] https://www.cnet.com/news/facebook-tries-googles-webp-image-format-users-squawk/ https://www.cnet.com/news/facebook-tries-googles-webp-image-... [2] http://arstechnica.com/information-technology/2013/04/chicken-meets-egg-with-facebook-chrome-webp-support/ http://arstechnica.com/information-technology/2013/04/chicke...