Introduction
This package is developed by Wildcard Corp. to provide the CDN Level(3) support with Plone. It provides a configuration panel to allow you to automatically invalidate the cache for an object or to do it manually and to configure your API settings.
To use this you need to setup your own API key, secret and figure out access group and property name for what you’d like to invalidate.
Wildcard is not affiliated with Level(3) Technologies and this product is not endorsed by Level(3). We just thought it might be useful to others contemplating using plone with Level(3) or any other CDN.
Changelog
1.3 (2013-08-14)
update for new version of level3 web service API
1.3b1 (2013-05-07)
plone 4.3 compatibility
1.3a2 (2012-04-23)
better error handling
handle duplicates
1.3a1 (2012-04-11)
add event argument to custom validator method
1.2a1 (2011-10-14)
add ability to do custom invalidator methods
1.1a5 (2011-08-24)
when generating auto string, make sure to convert to ascii.
1.1a4 (2011-07-21)
plone 4 fixes
1.1a3 (2011-07-11)
fixed issue in invalidating root
fixed error handling
use event when manually purged
1.1a2 (2011-03-30)
do not invalidate when object is removed–gets messy
1.1a1 (2011-03-29)
- provide ability to ignore certain paths to be
invalidated.
1.0a1 (2011-03-28)
Initial release
5 maintainers
Metadata
5 maintainers
Release files for wildcard.level3caching 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wildcard.level3caching-1.3.zip | 27.2 kB | Without provenance | Details for wildcard.level3caching-1.3.zip |
Release files / wildcard.level3caching-1.3.zip
| Download URL | wildcard.level3caching-1.3.zip |
|---|---|
| Size | 27.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ac5cd49297ff5ee8f23cf603728b97f121ada77c56fe2d0f04d819ba79905b2
|
|
BLAKE2b-256 checksum How to use checksums |
ca76ed6e8c82553b637501f4479c402b0b441a80e06dc3e0312e6572a52ceea2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wildcard.level3caching 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
