Photos are JPEG images, but they are all called image without extension. This means that your server does not provide them with a Content-Type image. Instead, the server sends an HTTP header:
Content-Type:application/octet-stream
Chrome and Firefox are apparently smart enough to notice that the request comes from the <img> element and recognize the JPEG format from the binary content itself. But you will make it a lot easier if you get a server to send a more appropriate header:
Content-Type:image/jpeg
I have two guesses:
- If you rename your photos on the server from
image to image.jpg or image.jpeg , then your server will select the correct content type and - Given the correct Content-Type IE will display the photos.
Oh wait, Amazon S3. I think the S3 web service will infer the Content-Type from the file extension, but if you cannot explicitly set the metadata on S3 objects , including (especially) the Content-Type.
source share