Closed ElectronicByte closed 10 years ago
@egelmex This is a problem with AWS serving .svg files with the wrong MIME type
curl -i http://www.tinkersoc.org/assets/images/2014-06-14-BarCamp-Canterbury/barcamp.svg
gives:
x-amz-id-2: M+JqQf15so58RDBa7gKCa6tR/0pGahk8EAk/QXKqfkWXXrZqtR/T0Hx7keawm9A9
x-amz-request-id: 772D045CAE63A6D1
Date: Mon, 07 Jul 2014 00:05:40 GMT
x-amz-meta-s3cmd-attrs: uid:1001/gname:users/uname:tinker/gid:100/mode:33188/mtime:1403601379/atime:1402826589/md5:6038422f9814b6a11696c3700c4cd444/ctime:1403601379
Last-Modified: Tue, 24 Jun 2014 09:46:46 GMT
ETag: "6038422f9814b6a11696c3700c4cd444"
Content-Type: binary/octet-stream
Content-Length: 10799
Server: AmazonS3
It should produce
Date: Mon, 07 Jul 2014 00:06:31 GMT
Server: Apache/2.2.22 (Debian)
Last-Modified: Sat, 14 Jun 2014 15:39:31 GMT
ETag: "1ce04bc-2a2f-4fbcd99a205b3"
Accept-Ranges: bytes
Content-Length: 10799
Cache-Control: max-age=31536000
Expires: Tue, 07 Jul 2015 00:06:31 GMT
Content-Type: image/svg+xml
Note the correct MIME type of image/svg+xml
in the correct header.
the image in the BarCamp post isn't showing