repoze.vhm README
This package provides middleware and utilities for doing virtual hosting within a WSGI/Repoze environment. It is particularly useful within a repoze.zope2 environment, where it may be used as an alternative to the classic VirtualHostMonster: method of doing virtual hosting.
Read the docs locally (see docs/index.rst), or read them online. repoze.vhm Changelog ====================
0.15 (2018-02-14)
Add support for testing on Travis.
Drop support for Python 2.6.
Add support fo Python 3.4, 3.5, and 3.6.
0.14 (2012-03-24)
Ensure HTTP_HOST is set correctly for non-standard ports under VHM paths. This header requires a trailing port if not the default for a given service. See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23. [davidjb]
0.13 (2010-04-18)
add conserve_path_infos for the VHMPathFilter middleware [kiorky]
0.12 (2010-01-01)
Update tests of middleware to check only that munge is called correctly.
Test munge sepearately.
100% test coverage.
fixed xheaders filter to set PATH_INFO correctly [vangheem]
0.11 (2009-08-31)
Add a repoze.vhm#vhm_explicit filter. This is like the vhm_xheaders middleware, but the VHM host and/or root are set in the WSGI configuration instead of in the request.
Calculate a VIRTUAL_URL and put it into the environment. This is basically the URL that the end user sees. repoze.zope2 >= 1.0.2 uses this to compute the ACTUAL_URL request variable, for example.
0.10 (2009-08-26)
Apply the HTTP_HOST port number fix to the VHM Path filter as well.
0.9 (2009-07-09)
0.8 (2009-01-10)
Set ‘HTTP_HOST’ in environ to the same value as ‘SERVER_NAME’, FBO apps which need it.
0.7 (2008-05-07)
Remove ‘dependency-links=’ to dist.repoze.org to prevent easy_install from searching there inappropriately.
0.6 (2008-04-17)
Re-added the path-segment-based filter as an option, to support scenarios in which the reverse proxy can be configured to rewrite the URL but not to add headers.
0.5 (2008-03-09)
Brown bag release: I fudged the entry point for the xheaders filter.
0.4 (2008-03-09)
Kill off path-segment-based filter (repoze.vhm.zope2). Only the xheaders filter remains.
Add license headers.
The middleware now sets a ‘repoze.vhm.virtual_host_base’ which is preferred by setServerUrl over ‘HTTP_HOST’ when present.
Add a getVirtualRoot API.
0.3 (2007-10-25)
Fix setServerURL method to take into account HTTP_HOST passed by client.
0.2 (2007-09-22)
Change repoze.vhm.zope2:setServerURL to allow Zope 2 to generate the correct request[‘URL’] value when the vhm is in the pipeline.
0.1 (2007-09-21)
Initial release.
Metadata
Release files for repoze.vhm3 0.15
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 |
|---|---|---|---|---|
| repoze.vhm3-0.15.tar.gz | 24.2 kB | Without provenance | Details for repoze.vhm3-0.15.tar.gz |
Release files / repoze.vhm3-0.15.tar.gz
| Download URL | repoze.vhm3-0.15.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0648253db1dbc8012c64dbe42eb95aecc1acd55f1f20858b6f90ef635829587d
|
|
BLAKE2b-256 checksum How to use checksums |
905eef6cbb87d3edd21d132571167253808dfd724904b206aa711d91b13a3f58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repoze.vhm3 0.15
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.