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.

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

New field: "Expires" #68

Open
joker314 opened this issue Jan 2, 2020 · 2 comments · May be fixed by #72
Open

New field: "Expires" #68

joker314 opened this issue Jan 2, 2020 · 2 comments · May be fixed by #72
Assignees

Comments

@joker314
Copy link
Collaborator

joker314 commented Jan 2, 2020

This is a new field which will be introduced by securitytxt/security-txt#183

This field indicates the date/time after which the data contained in the "security.txt"
file is considered stale and should not be used.
The value of this field follows the format defined in section 3.3 of {{!RFC5322}}.

This field MUST NOT appear more than once.

I'm thinking we should be able to accept a Date object, or an RFC5322 compliant timestamp. If something else is given, we can try to feed it to the Date constructor (so if an integer is given, it will be treated as milliseconds since 1970).

@lirantal
Copy link
Owner

lirantal commented Jan 3, 2020

Sounds good to me.

@bkimminich
Copy link

Added the directive via #70 but it accepts anything currently,

@joker314 joker314 linked a pull request Sep 9, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants