collective.redirect301
Thanks to plone.app.redirector Plone saves all URL changes that happen in the content and redirects the user to the proper content url.
It also allows the content-editor to create custom URLs for the content.
When doing so Plone uses a HTTP 302 status code to redirect the user to the new URL.
Sometimes you want those redirects to return a HTTP 301 status code, signaling that the redirect is Permanent.
There was a philosophical discussion when the status code was decided and the decission was to return a Temporary redirect.
This addon product, when enabled, changes that behavior and allows returning a Permanent redirect in such cases.
Installation
Install collective.redirect301 by adding it to your buildout:
[buildout]
...
eggs =
collective.redirect301
and then running bin/buildout
Finally you need to go to the Plone Addons Controlpanel and install the product there.
Contribute
Issue Tracker: https://github.com/collective/collective.redirect301/issues
Source Code: https://github.com/collective/collective.redirect301
Support
If you are having issues, please let us know.
License
The project is licensed under the GPLv2.
Contributors
Lur Ibargutxi, libargutxi@codesyntax.com
Changelog
1.0 (2023-07-19)
Initial release. [libargutxi]
1 maintainer
Metadata
1 maintainer
Release files for collective.redirect301 1.0
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 |
|---|---|---|---|---|
| collective.redirect301-1.0.tar.gz | 23.8 kB | Without provenance | Details for collective.redirect301-1.0.tar.gz |
Release files / collective.redirect301-1.0.tar.gz
| Download URL | collective.redirect301-1.0.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eea68db4a249ce828ad2e8e760194e8b34ec624f7b484cec459300f3394be217
|
|
BLAKE2b-256 checksum How to use checksums |
01cbce814f9456d7afb7d2addda9d98c185095fbd159081567a9511b407a15c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for collective.redirect301 1.0
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.
