httpx Drop `Origin` from public API. (Fix)

The Fix

Upgrade to version 0.13.0 or later.

Based on closed encode/httpx issue #656 · 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

@@ -26,7 +26,7 @@
     WriteTimeout,
 )
-from .models import URL, Cookies, Headers, Origin, QueryParams, Request, Response
+from .models import URL, Cookies, Headers, QueryParams, Request, Response
 from .status_codes import StatusCode, codes

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.13.0 or later.\nWhen NOT to use: This fix is not suitable if the `Origin` property is required for public API functionality.\n\n

Why This Fix Works in Production

Trigger: Minor breaking change here, although I'm not sure we *document* origin anywhere or not.
Mechanism: The `Origin` property was unnecessarily exposed in the public API
Why the fix works: Drops the `Origin` from the public API, including the removal of the `url.origin` property and the top-level export of `Origin`. (first fixed release: 0.13.0).

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

The `Origin` property was unnecessarily exposed in the public API
Production symptom (often without a traceback): Minor breaking change here, although I'm not sure we *document* origin anywhere or not.

Proof / Evidence

GitHub issue: #656
Fix PR: https://github.com/encode/httpx/pull/688
First fixed release: 0.13.0
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.78

Discussion

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

Jump to Sources Open on GitHub

“We don't really need to expose Origin publically. For the sake of keeping the public API space slim we should... * Drop the url.origin property. * Drop Origin from the top-level export. * Move Origin into utils.py. * Use origin = Origin(url”

Issue thread · issue description · source

Failure Signature (Search String)

Minor breaking change here, although I'm not sure we *document* origin anywhere or not.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Minor breaking change here, although I'm not sure we *document* origin anywhere or not.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Minor breaking change here, although I'm not sure we *document* origin anywhere or not.

What Broke

Exposing unnecessary properties can lead to confusion and misuse of the API.

Why It Broke

The `Origin` property was unnecessarily exposed in the public API

Fix Options (Details)

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

Upgrade to version 0.13.0 or later.

When NOT to use: This fix is not suitable if the `Origin` property is required for public API functionality.

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

First fixed release: 0.13.0

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

When NOT to Use This Fix

This fix is not suitable if the `Origin` property is required for public API functionality.

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.13.0	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.