DigitalOcean Spaces + `Connection: keep-alive` results in SignatureDoesNotMatch about awscr-signer HOT 2 OPEN

Hey, Sorry but I don't have any ideas. I thought maybe it should be a blacklisted header
https://github.com/taylorfinnell/awscr-signer/blob/master/src/awscr-signer/core/header_collection.cr#L16

But it does not appear to be in the official ruby client either
https://github.com/aws/aws-sdk-ruby/blob/master/gems/aws-sdk-s3/lib/aws-sdk-s3/presigner.rb#L13

But I don't see any specific handling of that header in this repo, or in the official ones

from awscr-signer.

I just saw #56 earlier this afternoon and realized I forgot to point out here that this signer was indeed having issues with Connection: keep-alive on AWS, not just on DO Spaces. It's just that I primarily use DO services so I just didn't see it happen on AWS as much, but I did notice it in a couple of my apps that use SQS.

This is blocking some important functionality in one of my new apps, so I'm trying Carl's suggested fix from #56 and I haven't gotten that error since I deployed it.

It makes me wonder if HTTP::Client reuses HTTP::Request instances when Connection: keep-alive is set. IIRC, HTTP::Server does reuse request and/or response instances with Connection: keep-alive to mitigate GC pressure, so I wouldn't be surprised if this is actually a bug where HTTP::Client doesn't requests properly.

from awscr-signer.