fix: label TLS-backend timeouts ServerTimeoutError, flatten noble multi headers, ValueError on unknown profile (v0.1.5)
Both backends' asyncio.TimeoutError except-branch was dead code (neither curl_cffi nor noble_tls raises it), so a real wire timeout fell through to the generic OSError branch and got mislabeled a plain aiohttp.ClientError instead of aioweb's own ServerTimeoutError contract; now detected via curl_cffi's Timeout type or Go-side timeout text and re-wrapped correctly. Noble's multi-valued response headers (e.g. two Set-Cookie lines) arrived as Python lists instead of strings, breaking any downstream .split()/.lower() call; now comma-joined per RFC 7230. An unknown Noble client profile string raised a raw AttributeError from the enum lookup; now a ValueError listing the valid profile names. Also compresses essay-length docstrings and narrating comments across the module with no behavior change. Signed-off-by: disqualifier <dev@disqualifier.me>
This commit is contained in:
+1
-1
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
|
||||
|
||||
[project]
|
||||
name = "aioweb_tls"
|
||||
version = "0.1.4"
|
||||
version = "0.1.5"
|
||||
description = "TLS-fingerprinting backends (curl_cffi / noble_tls) for aioweb via one injectable TLSSession, config-free, installable."
|
||||
requires-python = ">=3.10"
|
||||
dependencies = [
|
||||
|
||||
Reference in New Issue
Block a user