Proceedings of the 22nd International Conference on World Wide Web 2013
DOI: 10.1145/2487788.2488117
|View full text |Cite
|
Sign up to set email alerts
|

Archival HTTP redirection retrieval policies

Abstract: When retrieving archived copies of web resources (mementos) from web archives, the original resource's URI-R is typically used as the lookup key in the web archive. This is straightforward until the resource on the live web issues a redirect: R → R. Then it is not clear if R or R should be used as the lookup key to the web archive. In this paper, we report on a quantitative study to evaluate a set of policies to help the client discover the correct memento when faced with redirection. We studied the stability … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2015
2015
2017
2017

Publication Types

Select...
3

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 25 publications
0
3
0
Order By: Relevance
“…However, we cannot be sure until we dereference the URI-M and check its response headers for the values in rel="original" and Memento-Datetime. While it is unlikely that the IA will deceive us, the URI-M may redirect to another URI-M with a different Memento-Datetime, or in the case of an archived HTTP redirection, the URI-M might end up at an altogether different URI-R [3]. Furthermore, some archives issue URI-Ms without semantics -for example these URI-Ms are all mementos for google.com but neither this nor the Memento-Datetime can be ascertained without dereferencing: webcitation.org/query?id=1398456230796350, archive.is/sz8b9, and perma.cc/H3YY-BQN5.…”
Section: Opacity Of Uri-msmentioning
confidence: 99%
See 1 more Smart Citation
“…However, we cannot be sure until we dereference the URI-M and check its response headers for the values in rel="original" and Memento-Datetime. While it is unlikely that the IA will deceive us, the URI-M may redirect to another URI-M with a different Memento-Datetime, or in the case of an archived HTTP redirection, the URI-M might end up at an altogether different URI-R [3]. Furthermore, some archives issue URI-Ms without semantics -for example these URI-Ms are all mementos for google.com but neither this nor the Memento-Datetime can be ascertained without dereferencing: webcitation.org/query?id=1398456230796350, archive.is/sz8b9, and perma.cc/H3YY-BQN5.…”
Section: Opacity Of Uri-msmentioning
confidence: 99%
“…With archives that implement Memento, the Accept-Datetime header instructs the archive to return the originally archived status code (Section 6.1). AlSum et al [3] analyzed memento redirection patterns relating to HTTP redirects to supply the user with the correct memento when a redirect is encountered in the archives. They introduced the notion of "URI stability" to give a quantitative measure of the presence of HTTP 3XX status codes that result when URI-Ms in TimeMaps are dereferenced.…”
Section: Related Workmentioning
confidence: 99%
“…The research conducted so far has accepted the lists of URI-Ms in timemaps as ground truth; however, timemaps only tell part of the story. For example, a URI-M listed in a timemap may redirect to another with a different Memento-Datetime [5]. Redirections are likely to impact temporal coherence, which could change the coherence state of some eURI-Ms. Redirection could also be an indication of duplication; however, timemaps and archives provide no indication of cause for redirections, so we cannot be sure.…”
Section: Redirection and Missing Mementosmentioning
confidence: 99%