rfc6266
This module parses and generates HTTP Content-Disposition headers. These headers are used when getting resources for download; they provide a hint of whether the file should be downloaded, and of what filename to use when saving.
Usage
Receiver
parse_headers builds a ContentDisposition object from the Content-Disposition header and (as a fallback) the document location. Shortcuts work with response objects from httplib2 and the requests library.
Important attributes of ContentDisposition are is_inline, filename_unsafe, filename_sanitized.
Sender
build_header builds a header value from a filename.
Security
The Content-Disposition filename should be used with caution. Do not let the sender overwrite an arbitrary filesystem location, pick arbitrary extensions or filenames with special meaning, pick filenames containing unusual or misleading characters, etc. Read RFC 6266 section 4.3 for more details.
Testing
To test in the current Python implementation:
py.test
To test compatibility across Python releases:
tox
rfc6266 is currently tested under Python 2.7, Python 2.6, Python 3.3, Python 3.2, and PyPy (1.7).
References
RFC 6266 <https://tools.ietf.org/html/rfc6266> specifies the Content-Disposition header
RFC 5987 <https://tools.ietf.org/html/rfc5987> specifies a way to encode non-ascii filenames
TC 2231 <http://greenbytes.de/tech/tc2231/> is a test suite for Content-Disposition headers
1 maintainer
Metadata
1 maintainer
Release files for rfc6266 0.0.4
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 | |
|---|---|---|---|---|
| rfc6266-0.0.4.tar.gz | 8.1 kB | Without provenance | Details |
Release files / rfc6266-0.0.4.tar.gz
| Download URL | rfc6266-0.0.4.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
923116bd77cf283b161a813139f5022e894e91d040686208aa33eb43db1b7703
|
|
BLAKE2b-256 checksum How to use checksums |
b81e0f014fef1b09eb0b6dc5f10c1fcee9433cf33f53cc17ce66932e6d7babe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rfc6266 0.0.4
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.
