Add support for RFC822 timezone formatting for HeaderDateParser. #12
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.
While trying out the API against a newsgroup server I use, I ran into various header timezone strings that were failing to parse. I updated the timezone parsing to handle all cases specified in RFC822, as well as "UTC", which is not specified in the RFC but is a common timezone string nonetheless.
Additionally, I ran into a header date string that was suffixed with " (UTC)". Since this is another token, I updated the token-count validation logic for this specific case.