httpx URL.join behaviour is incorrect. (Fix)

The Fix

Upgrade to version 0.7.2 or later.

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

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -98,7 +98,8 @@ def __init__(
 
         # Normalize scheme and domain name.
-        self.components = self.components.normalize()
+        if self.is_absolute_url:
+            self.components = self.components.normalize()

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.7.2 or later.\nWhen NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.\n\n

Why This Fix Works in Production

Trigger: URL.join behaviour is incorrect.
Mechanism: Fixes the behavior of the URL.join method to align with RFC 3986 and Python's urljoin.
Why the fix works: Fixes the behavior of the URL.join method to align with RFC 3986 and Python's urljoin. (first fixed release: 0.7.2).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Production symptom (often without a traceback): URL.join behaviour is incorrect.

Proof / Evidence

GitHub issue: #142
Fix PR: https://github.com/encode/httpx/pull/144
First fixed release: 0.7.2
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.74

Discussion

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

Jump to Sources Open on GitHub

“Thoughts on using the built-in urljoin function (this is what urllib3 does)? Otherwise we could use rfc3986.URIReference.resolve_with() as well.”

@sethmlarson · 2019-07-25 · source

“Strongly prefer using resolve_with() which is what the intent already is: https://github.com/encode/httpx/blob/master/httpx/models.py#L201 Evidently not quite right tho.”

@lovelydinosaur · 2019-07-25 · source

Failure Signature (Search String)

URL.join behaviour is incorrect.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
URL.join behaviour is incorrect.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
URL.join behaviour is incorrect.

What Broke

Incorrect URL joining led to unexpected URL resolutions, causing broken links.

Fix Options (Details)

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

Upgrade to version 0.7.2 or later.

When NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.

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/144

First fixed release: 0.7.2

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

When NOT to Use This Fix

Do not use if it changes public behavior or if the failure cannot be reproduced.

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.

Version Compatibility Table

Version	Status
0.7.2	Fixed

Related Issues

No related fixes found.

Cluster: httpx:configuration-error All hubs All clusters

Related clusters: Data consistency Other Timeout

Sources

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