Deadlock when calling the code from an asp.net 4.8 web forms code behind about aws-signature-version-4 HOT 7 CLOSED

Confirmed to work, thanks for the fast fix.

from aws-signature-version-4.

Hi there and welcome to this repository!

A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it.

from aws-signature-version-4.

Hi @ronenfe and thanks for reporting this.

A couple of questions helping me reproduce this:

1. Is request targeting a recipient that is available on the network? I.e. should the request succeed but instead hangs?
2. Does it hang forever or does it finally throw an exception?

from aws-signature-version-4.

Yes, this code works if I copy the signing code out of the nuget and put it inside my project and make all calls sync except the call for the original httpclient which I use for it .ConfigureAwait(false).GetAwaiter().GetResult() because it also doesn't have a sync send for .net 4.x Maybe adding another method for sync signing in the nuget will work. I did a pull request on the other nuget for aws singing which I was part of writing it, but the owner doesn't approve it because he thinks it's unsafe , maybe you want to implement it the same way. tsibelman/aws-signer-v4-dot-net#37 (comment)
The code never returns from the nuget, no exception, it just get hung.

from aws-signature-version-4.

I've found the bug and will start working on fixing it in the upcoming days. Thanks for reporting it!

from aws-signature-version-4.

This issue has now been fixed in v3.0.1. Thank you for reporting this issue!

from aws-signature-version-4.

from aws-signature-version-4.