tigrcorn-http 0.3.16.dev11

HTTP utilities for Tigrcorn headers, entity tags, content coding, range requests, and Python web server responses.

tigrcorn-http

HTTP utilities for Tigrcorn headers, entity tags, content coding, range requests, and Python web server responses.

Install

uv add tigrcorn-http

pip install tigrcorn-http

Use the aggregate tigrcorn distribution when you want the full ASGI3 Python web server stack. Install tigrcorn-http directly when you want only this package boundary and its declared dependencies.

What It Owns

tigrcorn-http owns structured fields, range requests, entity validators, alt-svc, and early hints. Its import package is tigrcorn_http, and its declared package dependencies are: tigrcorn-core.

This package page is written for developers searching for Tigrcorn ASGI3 server components, Python web server packages, HTTP/3 and QUIC support, WebSocket and WebTransport-adjacent surfaces, and Apache 2.0 licensed infrastructure.

Why Use This?

Use tigrcorn-http when you want the http layer as a direct install target instead of the full server bundle. It lets application, operator, or certification workflows depend on this boundary explicitly while keeping the broader Tigrcorn runtime assembled from smaller repo-owned package surfaces.

FAQ

What does this package export?

The package exports through the tigrcorn_http namespace and keeps the root tigrcorn package as the compatibility umbrella.

Which boundary does this package own?

It is the package boundary for structured fields, range requests, entity validators, alt-svc, and early hints in the Tigrcorn package graph.

Which HTTP concerns live here?

This package owns structured fields, entity tags, range handling, conditional request logic, Alt-Svc helpers, Early Hints helpers, and related response-semantic utilities.

Features

• Owns structured fields, range requests, entity validators, alt-svc, and early hints inside the Tigrcorn split-package architecture.
• Publishes the tigrcorn_http import surface for named public helpers and entrypoints.
• Declared runtime dependencies: tigrcorn-core.
• Optional dependency surface: brotli.
• Supports Python 3.10, 3.11, 3.12, 3.13, and 3.14.

Use It When

Use tigrcorn-http when you need http-level behavior without pulling the entire server stack into the import surface. It is part of Tigrcorn's split-package architecture, so it can be installed independently while remaining linked to the rest of the Tigrcorn package family on PyPI.

Import Surface

from tigrcorn_http import format_etag, generate_entity_tag

etag = generate_entity_tag(b"hello")
print(format_etag(etag))

Namespace discovery starts with import tigrcorn_http.

The package exposes its supported public surface through the tigrcorn_http namespace. The root tigrcorn package keeps compatibility shims for users who install the full server distribution.

Related Packages

• tigrcorn-core
• tigrcorn

Package Graph

tigrcorn-core | tigrcorn-config | tigrcorn-http | tigrcorn-asgi | tigrcorn-contract | tigrcorn-transports | tigrcorn-security | tigrcorn-protocols | tigrcorn-static | tigrcorn-observability | tigrcorn-runtime | tigrcorn-compat | tigrcorn-certification

Best Practices

• Use these helpers for ETag, range, and conditional semantics instead of reimplementing HTTP edge logic in handlers.
• Keep entity and response-semantics changes aligned with the documented HTTP boundary.
• Pull optional content-coding dependencies only when your deployment actually needs them.

License

Apache-2.0