Page MenuHomeSoftware Heritage
Files F9123601

uri-scheme-browse.rst
No OneTemporary
Actions

uri-scheme-browse.rst
View Options

URI scheme for swh-web Browse application
=========================================
This web application aims to provide HTML views to easily navigate in the archive,
thus it needs to be reached from a web browser.
If you intend to query the archive programmatically through any HTTP client,
please refer to the :ref:`swh-web-api-urls` section instead.
Context-independent browsing
----------------------------
Context-independent URLs provide information about objects (e.g.,
revisions, directories, contents, person, ...), independently of the
contexts where they have been found (e.g., specific repositories,
branches, commits, ...).
The following endpoints are the same of the API case (see below), and
just render the corresponding information for user consumption. Where
hyperlinks are created, they always point to other context-independent
user URLs:
* :http:get:`/browse/content/[(algo_hash):](hash)/`: Display a content
* :http:get:`/browse/content/[(algo_hash):](hash)/raw/`: Get / Download content raw data
* :http:get:`/browse/directory/(sha1_git)/`: Browse the content of a directory
* :http:get:`/browse/revision/(sha1_git)/`: Browse a revision
* :http:get:`/browse/revision/(sha1_git)/log/`: Browse history log heading to a revision
Context-dependent browsing
--------------------------
Context-dependent URLs provide information about objects, limited to
specific contexts where the objects have been found.
For instance, instead of having to specify a (root) revision by **sha1_git**, users might want to
specify a place and a time. In Software Heritage a "place" is an origin, with an optional
branch name; a "time" is a timestamp at which some place has been observed by
Software Heritage crawlers.
Wherever a revision context is expected in a path (i.e., a
**/browse/revision/(sha1_git)/** path fragment) we can put in its stead a path fragment
of the form **/browse/origin/?origin_url=(origin_url)&timestamp=(timestamp)&branch=(branch)**.
Such a fragment is resolved, internally by the archive, to a revision **sha1_git** as follows:
- if **timestamp** is not given as query parameter: look for the most recent crawl of origin
identified by **origin_url**
- if **timestamp** is given: look for the closest crawl of origin identified
by **origin_url** from timestamp **timestamp**
- if **branch** is given as a query parameter: look for the branch **branch**
- if **branch** is absent: look for branch "HEAD" or "master"
- return the revision **sha1_git** pointed by the chosen branch
The already mentioned URLs for revision contexts can therefore be alternatively
specified by users as:
* :http:get:`/browse/origin/directory/`
* :http:get:`/browse/origin/content/`
* :http:get:`/browse/origin/log/`
Typing:
- **origin_url** corresponds to the URL the origin was crawled from,
for instance https://github.com/(user)/(repo)/
- **branch** name is given as per the corresponding VCS (e.g., Git) as
a query parameter to the requested URL.
- **timestamp** is given in a format as liberal as possible, to uphold the
principle of least surprise. At the very minimum it is possible to
enter timestamps as:
- ISO 8601 timestamps (see for instance the output of ``date -I``, ``date -Is``)
- YYYY[MM[DD[HH[MM[SS]]]]] ad-hoc format
- YYYY[-MM[-DD[ HH:[MM:[SS:]]]]] ad-hoc format
swh-web Browse Urls
-------------------
.. include:: uri-scheme-browse-content.rst
.. include:: uri-scheme-browse-directory.rst
.. include:: uri-scheme-browse-origin.rst
.. include:: uri-scheme-browse-release.rst
.. include:: uri-scheme-browse-revision.rst
.. include:: uri-scheme-browse-snapshot.rst

File Metadata

Mime Type
text/plain
Expires
Sat, Jun 21, 5:46 PM (1 w, 6 d ago)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
3237513

Event Timeline

About · Developer information · Legal