Files
replayweb.page/docs/supported-locations.md
T
Ilya Kreymer 220d14aea3 jekyll: move jekyll back to root, but simpler setup, exclude via _config.yml
app: bundle jekyll docs into app, add 'yarn run docs' to build
ui: add back/forward arrows for app only, adjust responsiveness for app, add IS_APP flag injected via preload
ui: add animated logo, friendly message on empty replay frame
app: improve serve logic:
- serve static files from static root
- serve replay from http localhost instead to avoid proxying https for remote requests
- serve local lookup from http prefix also
- catch any fallthrough from replay as 404
- add timestamp to response channels to ensure uniqness
2020-05-21 18:49:26 -07:00

2.9 KiB

layout, title, nav_order, description, parent, permalink
layout title nav_order description parent permalink
default Supported Locations 1 Supported Locations Reference /docs/locations

Supported Location URLs

ReplayWeb.Page uses URLs to uniquely indentify web archives.

In addition HTTP/S, the system supports loading from additional cloud providers and via peer-to-peer decentralized services. The goal is to support loading web archives from any source a web browser can connect to.

The following is a list of currently supported URL schemes and details below:

Scheme Status
https:// Supported
http:// Supported
file:// Supported
s3:// Supported
googledrive:// In progress
ipfs:// Partial
dat:// Planned

HTTP and HTTPS

While https://replayweb.page can load from any url, a site must allow access by enabling CORS for the web archive. HTTP URLs may not be accessible from https://replayweb.page since it requires HTTPS.

If you need to provide access to web archives stored on your own domain or over HTTP, consider deploying a copy on your server. See: Running your Own.

Local Files

Local files selected via the UI file chooser, and will be given a file:// URL. Unlike other web archive URLs, file URLs can not be shared with others.

Amazon S3

The s3:// url scheme is provided as a convenience to reference S3 URLs. The URL is converted to an HTTPS URL for access. The S3 Bucket must be public and also provide access to https://replayweb.page via CORS. Downloading via S3 credentials is not currently supported.

Google Drive

The googledrive:// url scheme is used when accessing a web archive shared over google drive. It provides a unique identifier provided via Google Drive. When accessing a google drive URL, the user will be asked to authenticate to be able to access the file.

IPFS

{: .d-inline-block }

Help Wanted {: .label .label-yellow }

The ipfs:// url scheme is provide as a convenience and resolves to using the Cloudflare IPFS Gateway to download archives from IPFS. A better implementation with IPFS directly is also possible.

DAT

{: .d-inline-block }

Help Wanted {: .label .label-yellow }

Support for dat:// is planned to allow true peer-to-peer transfer of web archives.