pyrfc6266
RFC6266 implementation in Python
Decision gist · record as of 2026-08-14
Yes, if you need RFC 6266 parsing and can accept abandoned maintenance. The package is stable for its narrow use case, has no known vulnerabilities, and low install friction. However, be aware it will not receive updates or bug fixes—only install if the current implementation meets your needs and you're comfortable maintaining a fork if issues arise.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Low install friction with a single lightweight dependency on pyparsing.
- However, the package is in abandoned maintenance status with no releases since April 2022 and the last commit in April 2023, so it will not receive bug fixes or updates.
License · maintenance · safety
MIT (permissive) — MIT license is permissive, allowing use in commercial and private projects with minimal restrictions—you need only include the license text in distributions.
last release 2022-04-29 (1568 days) · last repo commit 2023-04-28 · 14 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 76,775 downloads/mo, #14,591 on PyPI
Alternatives
Verify before relying
pip install pyrfc6266
import pyrfc6266
result = pyrfc6266.parse('attachment; filename="foo.html"')
filename = pyrfc6266.parse_filename('attachment; filename="foo.html"')- Whether the package handles all RFC 6266 edge cases and modern Content-Disposition variants correctly
- Compatibility with current versions of requests library if using the requests integration
What it is and what it does
pyrfc6266 is a Python parser for RFC 6266 Content-Disposition headers, designed as a replacement for older implementations that relied on the LEPL parsing library. It uses pyparsing to extract structured information from HTTP Content-Disposition headers, which are commonly used to specify how browsers should handle file downloads and attachments.
The package provides three main functions: parsing a header into its disposition type and parameters, extracting just the filename from a header, and extracting the filename directly from a requests response object. It's useful when handling file downloads where you need to recover the intended filename from HTTP response headers rather than relying on URLs.
Use it for
- Extract download filenames from HTTP responses when the filename comes from a Content-Disposition header
- Parse attachment headers in email or HTTP contexts to determine disposition type and parameters
- Build download managers or file-handling utilities that need RFC 6266 compliant filename extraction
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need RFC 6266 parsing and can accept abandoned maintenance.
The package is stable for its narrow use case, has no known vulnerabilities, and low install friction. However, be aware it will not receive updates or bug fixes—only install if the current implementation meets your needs and you're comfortable maintaining a fork if issues arise.
Install
pyrfc6266 on PyPI
Before you install
Low install friction with a single lightweight dependency on pyparsing. However, the package is in abandoned maintenance status with no releases since April 2022 and the last commit in April 2023, so it will not receive bug fixes or updates.
License in practice
MIT license is permissive, allowing use in commercial and private projects with minimal restrictions—you need only include the license text in distributions.
Quickstart
pip install pyrfc6266
import pyrfc6266
result = pyrfc6266.parse('attachment; filename="foo.html"')
filename = pyrfc6266.parse_filename('attachment; filename="foo.html"')Verify before relying
- Whether the package handles all RFC 6266 edge cases and modern Content-Disposition variants correctly
- Compatibility with current versions of requests library if using the requests integration
Package facts
| License | MIT permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagepyparsing |
| Maintenance | Abandoned 1,568 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 76,775 / month, #14,591 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaLicense :: OSI Approved :: MIT License |
Evidence: pyrfc6266-1.0.2-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “rfc 6266 content-disposition parser”
- pyrfc6266Parses RFC 6266 Content-Disposition headers to extract filename and…
- abnfGenerates parsers from ABNF grammars as specified in RFC 5234 and RFC…
- rfc3339Formats and parses dates according to RFC 3339, the Internet…
Give your agent the search over MCP, or paste the wish link into any chat.
More WWW/HTTP packages
urllib3 is an HTTP client library that provides thread-safe connection pooling, SSL/TLS verification, multipart file uploads, request retries, compression support, and proxy handling for Python applications.
Requests is a Python HTTP library that simplifies sending HTTP/1.1 requests with automatic handling of headers, authentication, cookies, and response parsing.
h11 is a pure-Python HTTP/1.1 protocol implementation that handles parsing and serializing HTTP messages without any built-in I/O, letting you integrate it with any network layer you choose.
HTTPX is a fully featured HTTP client library for Python that provides both sync and async APIs, with support for HTTP/1.1 and HTTP/2, plus an integrated command-line client.
Install it if you are building new projects or modernizing existing ones that rely on HTTP.
A minimal low-level HTTP client library that sends HTTP requests with thread-safe and task-safe connection pooling, supporting HTTP/1.1, HTTP/2, proxies, and both sync and async interfaces.
aiohttp is an async HTTP client and server framework built on asyncio, supporting both WebSockets and middleware-based routing for building concurrent web applications.
Install it if you need async HTTP client or server capabilities in asyncio-based applications.
See also mail-parser · cookies · django-ranged-response · tnefparse · git-url-parse · http-sf · uritools · mediatype · pyRFC3339 · rfc3986