amazon web services - 413 error from S3 presigned URL eventhough upload is successful - Stack Overflow

admin管理员组

文章数量:1391951

I have an application running both locally and in AWS using elastic beanstalk. For some reason, every now and then instead of having a successful upload from both my local version and elastic beanstalk version, I get a 413 error back from the upload. The weirdest thing is that the upload is successful so there should be nothing wrong with the configuration.

The error returned looks like this:

Failed to load resource: Origin is not allowed by Access-Control-Allow-Origin. Status code: 413

Sometimes the error is only on my elastic beanstalk version and sometimes it's only on my local version.

If I use the presigned URL generated manually I get this error:

413 ERROR
The request could not be satisfied.

Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: GGMScLnvvivvgq3vwoMKTBgs4nQ2-ZQ_5O8nplWH2mDNj9LQtYn8_w==

which I don't understand as I'm not even using cloudfront to upload these files.

本文标签： amazon web services413 error from S3 presigned URL eventhough upload is successfulStack Overflow