Signing with InvariantCulture, so different calendars produce good ou… #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…tput.
For example, in Thailand they are 543 years ahead, when formatting a date using
date.ToString("yyyyMMdd")
, it will produce25640129
. The library needs to format using the invariant culture to avoid issues with different calendars falling out of sync with AWS.The test is not great but I've included it so the issue is easy to reproduce. To make it more elegant I would need to extract
DateTime.UtcNow
fromSignV4Util.cs
which it's quite a bigger change.