Re: Using AWS s3 to host a document created by the composer

[Michael Aufreiter]

I’ve seen that same error once. Can you send me the source doc as a zip file. Will investigate.

—

Michael Aufreiter

Substance | http://substance.io

On Friday 21 March 2014 at 13:19, Ian Mulvany wrote:

I'm testing hosting a substance composer created doc on AWS s3. 

I've uploaded the contents of the zip file to http://substance.mulvany.net.s3-website-us-east-1.amazonaws.com/, but nothing is showing up (it's serving index.html all right, but there is not invoking the interface. 

You can verify that some of the resrouces have been uploaded (https://s3.amazonaws.com/substance.mulvany.net/figure_e0287b7adcbd050918eb93f9909e645a.png). 

I'm not sure exactly what's happening, should I be running this off of a web server, rather than statically? 

These files do work when run locally of my machine using the simple python web server. 

--
You received this message because you are subscribed to the Google Groups "Substance" group.
To unsubscribe from this group and stop receiving emails from it, send an email to substance_+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Graham Nott]

I've encountered an error like that before on S3. 

When you create an object with .json file extension, S3 by default sets the Content-Type as application/octet-stream.  You can see this in Chrome explorer.

To fix it in S3, you must change the Content-type to application/json  E.g. http://lens.elifesciences.org/manual/content.json