uppy/website
Manuel Kießling b03613d8bd
Update aws-s3.md wrt S3 public access settings
In my case, following the Uppy S3 documentation related to CORS by the letter still resulted in 403 responses with `AccessDenied` from my bucket's HTTP endpoint when my browser tried to upload a file.

It seems like S3 introduced an additional layer of security which generally overrides any public access settings in other places to protect inexperienced S3 users from accidentially making content in their S3 buckets public - at least this is my interpretation.

Therefore I extended the docs to inform Uppy users about the additional measures they potentially need to take.
2019-01-10 21:00:02 +01:00
..
private_modules/hexo-renderer-uppyexamples Update from master 2016-02-01 00:53:55 -05:00
scripts website: Load all prism languages (#1004) 2018-08-16 11:36:39 +02:00
src Update aws-s3.md wrt S3 public access settings 2019-01-10 21:00:02 +01:00
themes/uppy anonymizeIp in GA 2018-12-11 21:36:37 +03:00
_config.yml new demo video and gif, update frontpage code sample, design goals, add developed by transloasdit 2018-10-12 12:59:37 -04:00
build-examples.js Use src/ files in website examples. 2018-07-16 12:23:11 +02:00
doc-order.json Update from master 2016-02-01 00:53:55 -05:00
package-lock.json website: Update lockfile. 2018-08-16 14:44:02 +02:00
package.json Drop unused hexo-deployer-git. 2018-08-13 15:37:21 +02:00
update.js website: use html + add thumbnail-generator to bundle sizes 2018-07-19 14:04:23 +02:00
VUEORG_LICENSE Rename LICENSE to VUE 2015-11-29 14:22:03 +01:00