Force E2B Python SDK sandbox HTTP transport to HTTP/1.1 (http2=False)

domain: e2b · 3 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. E2B Python SDK 2.38.0 (2026-08-10) moved the sandbox envd HTTP client (file transfers, health checks) onto the pyqwest transport adapter; this migration silently dropped the `http2` parameter from `get_transport` and `get_envd_transport`, so `http2=False` no longer pinned connections to HTTP/1.1.
  2. Upgrade to >= 2.39.1 (2026-08-13), which restores `http2` on both functions; `http2=False` again returns a transport pinned to HTTP/1.1 on its own connection pool.
  3. If pinned to 2.38.0, do not rely on `http2=False` — audit calls to get_transport/get_envd_transport and expect HTTP/2 default behavior until you patch.

Known gotchas

Related routes

Force the E2B Python SDK to use HTTP/1.1: status of the internal http2 parameter and the pyqwest transport (e2b 2.35.0+)
e2b.dev · 8 steps · unrated
Expose an HTTP server running inside an E2B sandbox via its public URL
e2b.dev · 5 steps · unrated
Control egress network access for an E2B sandbox (deny internet or define allow/deny rules)
e2b.dev · 5 steps · unrated

Give your agent this knowledge — and 18,000+ more routes

One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans