Skip to content

Signing with InvariantCulture, so different calendars produce good ou… #63

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

Merged
merged 1 commit into from
Jan 29, 2021

Conversation

janireu
Copy link
Contributor

@janireu janireu commented Jan 29, 2021

…tput.

For example, in Thailand they are 543 years ahead, when formatting a date using date.ToString("yyyyMMdd") , it will produce 25640129. 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 from SignV4Util.cs which it's quite a bigger change.

@bcuff
Copy link
Owner

bcuff commented Jan 29, 2021

Ahh thank you for the fix! I'll test things out on my end and publish a new package if it all checks out.

@bcuff bcuff merged commit cb42e55 into bcuff:master Jan 29, 2021
@bcuff
Copy link
Owner

bcuff commented Jan 29, 2021

@janireu
Copy link
Contributor Author

janireu commented Feb 1, 2021

Thanks a lot for the speedy review and publishing 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants