-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Binary content does not POST. 408 error returned. #565
Comments
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. |
Hi @acurrieebix! Thank you for your detailed explanation. Let me see if I can reproduce it and fix the problem. |
I was able to reproduce the problem. Will continue to apply the fix. |
I've published a new version here. Could you please verify that it is solving your problem? Again, thanks for the issue description. It was spot on, and thus an easy issue to fix. |
An official version has been release on nuget.org. |
Thanks. Sorry I’m not going to be able to verify this under pressure on other areas. Thanks again for your quick responses.
Andrew
From: Mattias Kindborg ***@***.***
Sent: 25 June 2022 08:08
To: FantasticFiasco/aws-signature-version-4
Cc: Andrew Currie; Mention
Subject: Re: [FantasticFiasco/aws-signature-version-4] Binary content does not POST. 408 error returned. (Issue #565)
I've published a new version here<https://www.nuget.org/packages/AwsSignatureVersion4/4.0.0-beta.1>. Could you please verify that it is solving your problem?
Again, thanks for the issue description. It was spot on, and thus an easy issue to fix.
—
Reply to this email directly, view it on GitHub<#565 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM5DYFZWF3K6FLNQROQYXN3VQ2V6FANCNFSM5Y22VL3A>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
…________________________________
The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.
|
Passing a binary content will return 408 from the endpoint after a long wait.
To Reproduce
The following code will return a 408 from the service
Checking web debugging tool (e.g. fiddler) you can see the content of the request is empty.
Expected behavior
The request should be sent and processed.
Desktop (please complete the following information):
Windows 11 .net 6 console client.
Additional context
If you send base64 encoded StringContent rather than StreamContent, the request is successful.
The fix is to reset the stream back to the beginning. I suggest doing this when the content hash is created by adding the following at line 30 in ContentHashcs.
The text was updated successfully, but these errors were encountered: