-
Notifications
You must be signed in to change notification settings - Fork 317
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
AMAZON_AWS_S3_PKG "Duplicate Headers" #83
Comments
Just linking another discussion of the same issue: https://repost.aws/questions/QUUyrvzv0GRSyRQb7T9gXZhQ/error-duplicate-header-name-upon-put-to-s-3-bucket. |
Thanks for the feedback! I also started noticing this some weeks ago (actually, I can pinpoint the problem quite exactly to start appearing on February 24, 2023). I've had the same code running every day for many years doing backups, on the same "client" (database), so obviously this was something that changed on the AWS side. I looked at their docs and blogs, but could not find any mentions. I would variously see the error "Your request contains duplicate headers." returned from AWS, at other times I would just get "ORA-29273: HTTP request failed" lower down the stack. From what I could observe, uploading very small files would still work, while larger files fail. If the permanent fix is indeed to remove the "Host" header, I think I'll do a small refactoring of how the headers are set and commit a new version to Git when I have some free time. |
thanks! But now im getting - SignatureDoesNotMatch error Does somebody have fix for that? |
i found out that changing
to
also fixes duplicate header error, because 1.1 is automatically setting host header |
Are you calling amazon_aws_auth_pkg.init() first? |
Yes and my credentials are correct, i think its about not correct headers in signature? Not so sure.. |
Recently my code started failing with an error "Duplicate Headers" being returned from AWS, e.g. when uploading an object using AMAZON_AWS_S3_PKG.
Note: I was able to resolve this by editing the package to remove the bits that set the "Host" header. I don't know why that fixed it but it seems to work fine without this.
The text was updated successfully, but these errors were encountered: