Closed madisonkeene closed 7 years ago
OK dw i overreacted it's just a DNS issue because my bucket is too new... http://www.corrspt.com/blog/2016/01/17/uploading-to-amazon-s3-response-for-preflight-is-invalid-redirect-307/
but we should add something to the page where you connect s3 so people actually know this
Or even better, someone (not me, probably broad) should add some code so its able to deal with a redirect and still upload
Ok so now i'm hitting CORS issues... do users need to add a CORS policy now? surely not.
Have sent an email to ted/marco about this, its also a thing on the US genomespace.
Disclaimer also added to s3 connect page on gs-dev-au.
Workaround if need be- add CORS instructions to connect s3 page.
Added step to AWS connect instructions to set the CORS.
genomespace WHYYYYYYY