HTTPX2

HTTPX2 is the part of OpenAI's Python SDK (the ready-made toolkit developers use, essentially a box of prebuilt parts) that actually carries the mail back and forth with OpenAI's servers. This job used to belong to a component called HTTPX, but it has recently been swapped out for HTTPX2.

One of the courier's key jobs is checking ID to make sure the party on the other end is really OpenAI. Previously, it always carried a separate ID-verification list called certifi and checked against that. Starting with HTTPX2, it instead relies on the ID-verification list already built into the computer's operating system. The problem is that very minimal servers or certain special corporate environments may not have this built-in list at all, or may have an incomplete one. If that happens, the courier can't verify the other side's identity, and communication can get blocked entirely.

So developers working in such environments need to either install a certificate list on the machine themselves, or explicitly specify in their code which certificate list to use. On the surface, it looks like just one component's name changed, but under the hood, the way the connection verifies that the server is trustworthy has actually changed.

In articles, it shows up in phrasing like "OpenAI switched the default transport tool in the openai-python package from HTTPX to HTTPX2." It's easy to misread this as a new AI model or a ChatGPT feature update — it isn't. Regular ChatGPT users are unaffected; this only matters for the server environments of developers who connect OpenAI's features into their own programs.

If you're a developer working directly with code, here are some things to check:

1. If you suddenly get server connection errors after freshly installing the openai package, check whether the server or container you're using has an up-to-date certificate list (the ID-verification list) properly in place.
2. If you're in a special environment like a corporate internal network or a minimal container, check the documentation for an option to explicitly specify which certificate list to use in your code.
3. If you're using custom code or mock tools that intercept authentication or requests/responses, check whether they need to be updated to work with the new transport tool.