Easy to implement redirect middleware, which loads redirects from a configurable backend.
Installation
pip install readyrector
Usage
# settings.py
INSTALLED_APPS = (
# ...
'readyrector',
# ...
)
# put at the end of the middleware list as a last resort
MIDDLEWARE = (
# ...
'readyrector.middleware.RedirectDatabaseMiddleware',
)
RedirectDatabaseMiddleware
Gets redirects from database records. Implement a view or API to manage these records.
RedirectURLConfMiddleware
Gets redirects from a URL conf file. Requires setting READYRECTOR_URLCONF
Settings
READYRECTOR_URLCONF
Default: ''
Required when RedirectURLConfMiddleware is used. Expects a path to a URL conf file.
Metadata
Release files for readyrector 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 |
|---|---|---|---|---|
| readyrector-1.0.tar.gz | 6.0 kB | Without provenance | Details for readyrector-1.0.tar.gz |
Release files / readyrector-1.0.tar.gz
| Download URL | readyrector-1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06f2407416e831fb1c84ed62871f49b9d62de64f0286fa34d15f953b48501117
|
|
BLAKE2b-256 checksum How to use checksums |
c1af335ce0251c1f26980544dc871590f752866c1e738985b9795a9902be3146
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.5.0 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.14
|
Security for readyrector 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.