guillotine is a WSGI middleware which allows for HEAD requests to be properly handled by your WSGI pipeline. guillotine is intended to be placed as the first, or topmost component in a WSGI pipeline, such that all other middelware is downstream. For an incoming request, guillotine converts the request method from ‘HEAD’ to ‘GET’ before handing the request off to the next downstream middleware or application. guillotine then takes responsiblity for discarding the response body before returning to the application server.
For more information about why you might want to do this see Graham Dumpleton’s article, WSGI issues with HTTP HEAD requests.
Using guillotine with Paster
guillotine provides an entry point for Paster allowing it to be used as a middleware in a pipeline:
[pipeline:example_app]
pipeline =
egg:guillotine#guillotine
egg:example#some_middleware
example_app
Using guillotine “by hand”
If you compose your WSGI pipeline in Python code, guillotine can be constructed directly:
from guillotine import Guillotine middleware = Guillotine(app) # app is some WSGI application or pipeline
0.1 (2011-05-20)
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for guillotine 0.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 | |
|---|---|---|---|
| guillotine-0.1.tar.gz | 2.7 kB | Details |
Release files / guillotine-0.1.tar.gz
| Download URL | guillotine-0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1441b6ed4126daffacd68e876778b9871eb75944f19ab8a02944858752a2ae4
|
|
BLAKE2b-256 checksum How to use checksums |
67fa40f27b48a552ff7655789bf7dfcf413b55db5981ba8f066ac1dee9ccceef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
