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

Rudimentary Memento support on replay #11

Open
machawk1 opened this issue Feb 19, 2019 · 3 comments
Open

Rudimentary Memento support on replay #11

machawk1 opened this issue Feb 19, 2019 · 3 comments
Labels

Comments

@machawk1
Copy link

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.

@ato
Copy link
Member

ato commented Feb 19, 2019

Yep. I agree.

@ato ato added the idea label Feb 20, 2019
ato added a commit that referenced this issue Feb 20, 2019
@ato
Copy link
Member

ato commented Feb 20, 2019

We should also support the Accept-Datetime request header. Need index improvements (#12) for that.

ato added a commit that referenced this issue Feb 20, 2019
@machawk1
Copy link
Author

@ato I agree re:Accept-Datetime but I figured getting the capture/memento to report what it is would be a start for further negotiation.

For the endpoint that is receiving the Accept-Datetime header, be sure to have the Vary: Accept-Datetime in the response (see RFC7089 §2.1.2).

For the capture (memento) itself, you may also want to report a Link response header to relate the capture (at a URI-M) to the live web URI (URI-R) with rel="original", e.g., example in §4.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants