-
Notifications
You must be signed in to change notification settings - Fork 10
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
Rudimentary Memento support on replay #11
Comments
Yep. I agree. |
We should also support the |
@ato I agree re: For the endpoint that is receiving the For the capture (memento) itself, you may also want to report a |
I noticed that replaying WARCs provides a 14-digit datetime placeholder. As I anticipate this will eventually be semantic, it need not necessarily be. However, providing Memento (RFC7089) HTTP response headers would give some temporal context to the capture.
As a start, initially providing the Memento-Datetime HTTP response header (in RFC1123 format, e.g.,
Memento-Datetime: Fri, 09 Jan 2009 01:00:00 GMT
) when viewing a capture from the WARC would be useful for further integration into other systems.The text was updated successfully, but these errors were encountered: