Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle 2-digit years in RFC850 dates #4

Open
SevereOverfl0w opened this issue Apr 17, 2021 · 0 comments
Open

Handle 2-digit years in RFC850 dates #4

SevereOverfl0w opened this issue Apr 17, 2021 · 0 comments

Comments

@SevereOverfl0w
Copy link

(reap.decoders/http-date "Mon Jan 1 00:00:00 90") returns nil but should parse. In addition:

Recipients of a timestamp value in rfc850-date format, which uses a
two-digit year, MUST interpret a timestamp that appears to be more
than 50 years in the future as representing the most recent year in
the past that had the same last two digits.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SevereOverfl0w