Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SignatureDoesNotMatch Error #10

Open
fbeauchemin opened this issue Oct 26, 2018 · 4 comments
Open

SignatureDoesNotMatch Error #10

fbeauchemin opened this issue Oct 26, 2018 · 4 comments

Comments

@fbeauchemin
Copy link

Do you have any idea why I would get a SignatureDoesNotMatch error? CORS and everything are set properly... just can't make the demo work ...

@asagage
Copy link

asagage commented Nov 1, 2018

same here

@asagage
Copy link

asagage commented Nov 1, 2018

I got mine working. Turns it it was a CORS issue and I was getting the signature error when attempting to view the original request in my browser .

The cors policy I was able to use for testing was...
<CORSConfiguration> <CORSRule> <AllowedOrigin>*</AllowedOrigin> <AllowedMethod>PUT</AllowedMethod> <AllowedHeader>*</AllowedHeader> </CORSRule> </CORSConfiguration>

@fbeauchemin
Copy link
Author

No luck with that config but I managed to have it work with a barebone PUT without the Content-Type header when uploading. Specifying it when generating the pre-signed url didn't cause any issues.

At this point, I'm not sure who's to blame but dropzone.js seems to always set the Content-Type header, even when set to empty string or null.

@androidfanatic
Copy link

Setting responseType to text fixed it for me:

      sending(file, xhr) {
        let _send = xhr.send;
        xhr.responseType = "text";
        xhr.send = () => {
          _send.call(xhr, file);
        }
      },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants