We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a long lived HTTP connection times out and the http client has to reconnect the before_request will be executed again, but then there are already headers which I think this code will use: https://github.com/taylorfinnell/awscr-signer/blob/master/src/awscr-signer/signers/v4.cr#L83-L85
before_request
but that results in a InvalidSignatureException. It can be solved by deleting the headers first:
InvalidSignatureException
@http.before_request do |request| request.headers.delete "Authorization" request.headers.delete "X-Amz-Content-Sha256" request.headers.delete "X-Amz-Date" signer.sign(request) end
The text was updated successfully, but these errors were encountered:
iiiiinteresting. This sounds similar to the issue I've been having in #52. I'll try your solution in my shard and see if that helps.
Sorry, something went wrong.
Attempt to fix issue with Connection: keep-alive
5ca1401
See taylorfinnell/awscr-signer#56 (comment)
Connection: keep-alive
No branches or pull requests
When a long lived HTTP connection times out and the http client has to reconnect the
before_request
will be executed again, but then there are already headers which I think this code will use: https://github.com/taylorfinnell/awscr-signer/blob/master/src/awscr-signer/signers/v4.cr#L83-L85but that results in a
InvalidSignatureException
. It can be solved by deleting the headers first:The text was updated successfully, but these errors were encountered: