Introduction
collective.regexredirector extends the plone.app.redirector behavior to allow to define redirections using regular expressions.
It might be particulary useful if you migrate an old website and you want to map old urls to the new site structure.
Note: when a 404 occurs, collective.regexredirector first calls plone.app.redirector, and if it does not redirect, then collective.regexredirector tries to match one of its registered regular expressions.
Usage
In the Plone control panel, go to the “RegexRedirector” control panel and enter your redirection rules.
One redirection by line using the following format
'old_url'='new_url' 'old_url2'='new_url2'
Examples
Redirecting all urls like /news/something to /archives/index
'/news/.*'='/archives/index'
Redirecting all urls like /tags/something to /category/something
'/tags/(?P<category_name>.+)'='/category/\g<category_name>/view'
INSTALL
Add collective.regexredirector to your buildout eggs.
Credits
Companies
Changelog
0.2.3 (2015-05-26)
Fix bug when no match
0.2.2 (2015-05-12)
Supports redirection to url containing a querystring
Fix bug if rules contain ‘=’
0.2.1 (2013-03-28)
Fix egg (missing /docs)
0.2 (2013-03-28)
Fix egg (missing README.rst)
0.1 (2013-01-30)
Initial release
Release files for collective.regexredirector 0.2.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 |
|---|---|---|---|---|
| collective.regexredirector-0.2.3.zip | 22.8 kB | Without provenance | Details for collective.regexredirector-0.2.3.zip |
Release files / collective.regexredirector-0.2.3.zip
| Download URL | collective.regexredirector-0.2.3.zip |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f004f01a0e0367cfed469c6a1cb1251006e8bc3c62307995e1283b8049765b91
|
|
BLAKE2b-256 checksum How to use checksums |
0fff041b736c19b2438bd6796c6361cb498c6aded773968afe9d4e6ab1d99ef9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.regexredirector 0.2.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.
