httpx On `proxies={"http": ...}` vs. `proxies={"http://":

The Fix

Upgrade to version 0.14.0 or later.

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

@@ -284,8 +284,8 @@ For more advanced use cases, pass a proxies `dict`. For example, to route HTTP a
 ```python
 proxies = {
-    "http": "http://localhost:8030",
-    "https": "http://localhost:8031",
+    "http://": "http://localhost:8030",

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.14.0 or later.\nWhen NOT to use: This fix is not suitable if you require backward compatibility with existing proxy key formats.\n\n

Why This Fix Works in Production

Trigger: * Raising a warning on base usage of "all", "http", "https", later escalating this to an error.
Mechanism: The proxy key handling was inconsistent, allowing non-URL patterns
Why the fix works: Raises a warning if proxy keys like 'all' are used instead of 'all://'. (first fixed release: 0.14.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 proxy key handling was inconsistent, allowing non-URL patterns
Production symptom (often without a traceback): * Raising a warning on base usage of "all", "http", "https", later escalating this to an error.

Proof / Evidence

GitHub issue: #1105
Fix PR: https://github.com/encode/httpx/pull/1127
First fixed release: 0.14.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.69

Discussion

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

Jump to Sources Open on GitHub

“Hello @tomchristie , Are you talking about the changes in httpx._client.BaseClient._get_proxy_map (here: link) Also, what should we do with get_environment_proxies? (link) This function requires envs…”

@cdeler · 2020-08-04 · source

Failure Signature (Search String)

* Raising a warning on base usage of "all", "http", "https", later escalating this to an error.
Are you talking about the changes in `httpx._client.BaseClient._get_proxy_map` (here: [link](https://github.com/encode/httpx/blob/master/httpx/_client.py#L101))

Copy-friendly signature

signature.txt

Failure Signature
-----------------
* Raising a warning on base usage of "all", "http", "https", later escalating this to an error.
Are you talking about the changes in `httpx._client.BaseClient._get_proxy_map` (here: [link](https://github.com/encode/httpx/blob/master/httpx/_client.py#L101))

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
* Raising a warning on base usage of "all", "http", "https", later escalating this to an error.
Are you talking about the changes in `httpx._client.BaseClient._get_proxy_map` (here: [link](https://github.com/encode/httpx/blob/master/httpx/_client.py#L101))

What Broke

Using incorrect proxy keys led to unexpected behavior in HTTP requests.

Why It Broke

The proxy key handling was inconsistent, allowing non-URL patterns

Fix Options (Details)

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

Upgrade to version 0.14.0 or later.

When NOT to use: This fix is not suitable if you require backward compatibility with existing proxy key formats.

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

First fixed release: 0.14.0

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

When NOT to Use This Fix

This fix is not suitable if you require backward compatibility with existing proxy key formats.

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

httpx On `proxies={"http": ...}` vs. `proxies={"http://": ...}` (Fix)