pywb/sample_archive/access/pywb.aclj

org,iana)/about - {"access": "block"}
org,iana)/_css/2013.1/fonts/opensans-semibold.ttf - {"access": "allow"}
org,iana)/_css - {"access": "exclude"}
org,iana)/ - {"access": "exclude"}
org,example)/?example=1 - {"access": "block"}
- support for allow/block/exclude access controls (as per ukwa/ukwa-pywb#7) - .aclj files contain access controls in reverse sorted, CDXJ-like format - ./sample_archive/acl contains sample acl files - directory and single-file acl sources (extend directory aggregator and file index source) - tests for longest-prefix acl match - tests for acl applied to collection - pywb.utils.merge -- merge(..., reverse=True) support for py2.7 (backported from py3.5) - acl types: * allow - all allowed * block - allowed in index (as blocked) but content not allowed, served as 451 * exclude - removed from index and content, served as 404 - warcserver: AccessChecker inited if 'acl_paths' specified in custom collections - exceptions: * clean up wbexception, subclasses provide the status code, message loaded automatically * warcserver handles AccessException with json response (now with 451 status) * pass status to template to allow custom handling 2018-02-17 21:59:30 -08:00			`org,iana)/about - {"access": "block"}`
			`org,iana)/_css/2013.1/fonts/opensans-semibold.ttf - {"access": "allow"}`
			`org,iana)/_css - {"access": "exclude"}`
			`org,iana)/ - {"access": "exclude"}`
acl optimization: addresses ukwa/ukwa-pywb#38 - stop checking acl rules linearly if acl key < tld - use existing rule for same url (at least until date-range checking) 2019-02-14 12:15:15 -08:00			`org,example)/?example=1 - {"access": "block"}`