Access Control Improvements: Embargo + ACL User Support #642
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds an embargo system on top of the access control system, allowing blocking of all URLs based on capture date.
The embargo supports blocking:
When combined with ACL rules, the embargo takes precedence, unless the
allow_ignore_embargo
rule is used.The PR also adds an optional
user
field to the ACL system, allowing specific matches by user, passed to pywb via theX-pywb-ACL-user
header.Version bump to 2.6.0b0
Motivation and Context
Support for embargo system and custom -user based auth as part of work for:
https://netpreserve.org/projects/pywb/
Docs: Initial pass on updated docs for Embargo + ACL system.
Screenshots (if appropriate):
Types of changes
Checklist: