You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manual/access-control.rst
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ An .aclj file may look as follows::
95
95
96
96
Each JSON entry contains an ``access`` field and the original ``url`` field that was used to convert to the SURT (if any).
97
97
98
-
The JSON entry may also contain a ``user`` field, as explained below.
98
+
The JSON entry may also contain ``user``, ``before``, and ``after`` fields, as explained below.
99
99
100
100
The prefix consists of a SURT key and a ``-`` (currently reserved for a timestamp/date range field to be added later).
101
101
@@ -166,6 +166,23 @@ Further examples of how to set this header will be provided in the deployments s
166
166
See the :ref:`config-acl-header` section in Usage for examples on how to configure this header.
167
167
168
168
169
+
Date-Based Access Controls
170
+
^^^^^^^^^^^^^^^^^^^^^^^^^^
171
+
172
+
The access control rules can further be customized be specifying different permissions based on capture timestamp, using ``before`` and ``after`` fields that operate in the same manner as their embargo counterparts for a specific URL or domain.
173
+
174
+
For example, the following access control settings restrict access to ``https://example.com/restricted/`` by default, but allow access for captures prior to December 1, 2010::
Combined with the embargo settings, this can also be used to override the embargo for captures that fall within a particular time period, while keeping the embargo for general access::
0 commit comments