httpx Releasing 0.7.3 (Fix)

The Fix

Upgrade to version 0.7.3 or later.

Based on closed encode/httpx issue #359 · PR/commit linked

Open PR/Commit

@@ -1,5 +1,32 @@
 # Changelog
 
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.7.3 or later.\nWhen NOT to use: This fix should not be used if API guarantees are required under SemVer.\n\n

Why This Fix Works in Production

Trigger: - SSLKEYLOGFILE
Mechanism: Release 0.7.3 includes several new features and bug fixes, addressing issue #359.
Why the fix works: Release 0.7.3 includes several new features and bug fixes, addressing issue #359. (first fixed release: 0.7.3).

Why This Breaks in Prod

Production symptom (often without a traceback): - SSLKEYLOGFILE

Proof / Evidence

GitHub issue: #359
Fix PR: https://github.com/encode/httpx/pull/362
First fixed release: 0.7.3
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.85
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.75

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“I guess so? There aren't any API guarantees for 0.X under SemVer though.”

@sethmlarson · 2019-09-19 · source

“@florimondmanca FYI I added you to the PyPI project along with @yeraydiazdiaz. Didn't realize I was an Owner! :)”

@sethmlarson · 2019-09-20 · source

“Yep, definitely time to release. Maybe I'll try to get the proxy config PR in before but if not it's fine to ship without. :)”

@sethmlarson · 2019-09-19 · source

“Yes, it can make it in 0.7.4 too. :) I was wondering — what’s the policy for minor bumps? Breaking changes I guess?”

@florimondmanca · 2019-09-19 · source

Failure Signature (Search String)

- SSLKEYLOGFILE
I was wondering — what’s the policy for minor bumps? Breaking changes I guess?

Copy-friendly signature

signature.txt

Failure Signature
-----------------
- SSLKEYLOGFILE
I was wondering — what’s the policy for minor bumps? Breaking changes I guess?

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
- SSLKEYLOGFILE
I was wondering — what’s the policy for minor bumps? Breaking changes I guess?

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

Upgrade to version 0.7.3 or later.

When NOT to use: This fix should not be used if API guarantees are required under SemVer.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/encode/httpx/pull/362

First fixed release: 0.7.3

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

This fix should not be used if API guarantees are required under SemVer.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
Upgrade behind a canary and run integration tests against the canary before 100% rollout.
Add a TLS smoke test that performs a real handshake in CI (include CA bundle validation and hostname checks).
Alert on handshake failures by error string and endpoint to catch cert/CA changes quickly.

Version Compatibility Table

Version	Status
0.7.3	Fixed

Related Issues

No related fixes found.

Cluster: httpx:ssl-handshake All hubs All clusters

Related clusters: Configuration error Data consistency Other

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.