httpx API design question - `Response.url` (Fix)

The Fix

Upgrade to version 0.7.2 or later.

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

Open PR/Commit

@@ -204,7 +204,7 @@ def __hash__(self) -> int:
 
     def __eq__(self, other: typing.Any) -> bool:
-        return isinstance(other, URL) and str(self) == str(other)
+        return isinstance(other, (URL, str)) and str(self) == str(other)

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.7.2 or later.\nWhen NOT to use: This fix is not suitable if maintaining strict API compatibility with requests is not a priority.\n\n

Why This Fix Works in Production

Trigger: This is a breaking change from the requests API where it just exposes a plain string.
Mechanism: Allows string comparison for the URL class, enhancing API compatibility with requests.
Why the fix works: Allows string comparison for the URL class, enhancing API compatibility with requests. (first fixed release: 0.7.2).

Why This Breaks in Prod

Production symptom (often without a traceback): This is a breaking change from the requests API where it just exposes a plain string.

Proof / Evidence

GitHub issue: #113
Fix PR: https://github.com/encode/httpx/pull/139
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.73

Discussion

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

Jump to Sources Open on GitHub

“If we do keep it as a URL instance, then one option to keep closer API compat would be to allow string comparisons, eg URL(“https://www.encode.io/“)…”

@lovelydinosaur · 2019-07-09 · source

“Seems like it's probably the best all round option yeah.”

@lovelydinosaur · 2019-07-09 · source

“I'm for allowing string comparisons and providing the read-only URL instance. :) Seems like something users are probably doing themselves and shouldn't have to.”

@sethmlarson · 2019-07-09 · source

“I'd say that flags / parameters that massively alter the behavior of a function should probably be avoided. Typically what a lot of URL instance…”

@sethmlarson · 2019-07-10 · source

Failure Signature (Search String)

This is a breaking change from the requests API where it just exposes a plain string.
assert type(s.get("https://example.com").url) is str

Copy-friendly signature

signature.txt

Failure Signature
-----------------
This is a breaking change from the requests API where it just exposes a plain string.
assert type(s.get("https://example.com").url) is str

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
This is a breaking change from the requests API where it just exposes a plain string.
assert type(s.get("https://example.com").url) is str

What Broke

Users experience API compatibility issues when migrating from requests to httpx.

Fix Options (Details)

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

Upgrade to version 0.7.2 or later.

When NOT to use: This fix is not suitable if maintaining strict API compatibility with requests is not a priority.

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

Option D — Guard side-effects with OnceOnly Guardrail for side-effects

Mitigate duplicate external side-effects under retries/timeouts/agent loops by gating the operation before calling external systems.

Place OnceOnly between your code/agent and real side-effects (Stripe, emails, CRM, APIs).
Use a stable key per side-effect (e.g., customer_id + action + idempotency_key).
Fail-safe: configure fail-open vs fail-closed based on blast radius and spend risk.

Show example snippet (optional)

onceonly.py

from onceonly import OnceOnly
import os

once = OnceOnly(api_key=os.environ["ONCEONLY_API_KEY"], fail_open=True)

# Stable idempotency key per real side-effect.
# Use a request id / job id / webhook delivery id / Stripe event id, etc.
event_id = "evt_..."  # replace
key = f"stripe:webhook:{event_id}"

res = once.check_lock(key=key, ttl=3600)
if res.duplicate:
    return {"status": "already_processed"}

# Safe to execute the side-effect exactly once.
handle_event(event_id)

See OnceOnly SDK

When NOT to use: Do not use this to hide logic bugs or data corruption. Use it to block duplicate external side-effects and enforce tool permissions/spend caps.

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

First fixed release: 0.7.2

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

When NOT to Use This Fix

This fix is not suitable if maintaining strict API compatibility with requests is not a priority.
Do not use this to hide logic bugs or data corruption. Use it to block duplicate external side-effects and enforce tool permissions/spend caps.

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:other All hubs All clusters

Related clusters: Configuration error Data consistency Timeout

Sources

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