five.hashedresource
While we want browsers to cache static resources such as CSS-stylesheets and JavaScript files, we also want them not to use the cached version if the files on the server have been updated. (And we don’t want to make end-users have to empty their browser cache to get the latest version. Nor explain how to do that over the phone every time.)
To make browsers update their caches of resources immediately when the resource changes, the absolute URLs of resources can now be made to contain a hash of the resource’s contents, so it will look like /++noop++12345/@@/myresource instead of /@@/myresource.
In developer mode the hash is recomputed each time the resource is asked for its URL, while in production mode the hash is computed only once, so remember to restart the server after changing resource files (else browsers will still see the old URL unchanged and use their outdated cached versions of the files).
To use this package, include its configure.zcml and use five.hashedresource.interfaces.IHashedResourceSkin or a skin that inherits from it.
CHANGES
1.1 (2009-07-30)
Added a hack to communicate to ZCML whether Zope2 debug-mode is on.
1.0 (2009-07-27)
first released version
Release files for five.hashedresource 1.1
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 |
|---|---|---|---|---|
| five.hashedresource-1.1.tar.gz | 6.5 kB | Without provenance | Details for five.hashedresource-1.1.tar.gz |
Release files / five.hashedresource-1.1.tar.gz
| Download URL | five.hashedresource-1.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5ec3b009ae51ecc2687438204597b736d32a83fecaeccbb0e9654fc5ce241eb
|
|
BLAKE2b-256 checksum How to use checksums |
afa4a3dc8a72a0b65e1695681137e3eabc708bcd5aed6f78fc6f9c6958f43d63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for five.hashedresource 1.1
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.
