Fixed issues created by the date string being localized #2217
+44
−8
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.
Fixes #2215.
Since this implementation also involves stream locales, I thought it would be a good idea to replace char arrays with strings, as these arrays would be casted to strings anyway and require size managment that in current implementation is prone to fail (see the issue).
I've added an overload for string to function
datetoCustomFormattedString
and addedgetHttpFullDateStr
function, that does exactly the same asgetHttpFullDate
, but returns the string type.I've left old functions just-in-case, and adjusted github workflow as containers were missing en_US locale. Seems to be working fine.
Here is a minimal working example:
This is the program output:
and this is the request result from Postman: