Fix x-ms-date format issue for non-english locales #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aliuy
changed the title
shipunyc
added a commit
that referenced
this pull request
Jan 16, 2015
Fix x-ms-date format issue for non-english locales
kirankumarkolli
pushed a commit
that referenced
this pull request
Jan 19, 2018
minor update to .gitignore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Computers running on non-English locales may run in to a "com.microsoft.azure.documentdb.DocumentClientException: The input date header is invalid format. Please pass in RFC 1123 style date format." in which the x-ms-date fails server validation.
Details: https://social.msdn.microsoft.com/Forums/azure/en-US/de4ad792-6b58-42e7-803c-4c6f549094c0/documentdb-java-example-errors?forum=AzureDocumentDB
This fix is to use format the x-ms-date using Locale.US