Why RequestsHttpConnection Examples Do Not Fit Elasticsearch Python 8
Version 8 changed transport customization to node classes; match the installed HTTP implementation before diagnosing a later proxy connection.
An import or constructor failure involving RequestsHttpConnection/connection_class can be an API-generation mismatch before any proxy request. Elasticsearch Python 8 uses transport node classes and node_class.
Identify the installed major version and selected node implementation. Requests-backed and urllib3-backed nodes can handle proxy environment inputs differently. A standalone Requests success does not configure the session owned by the Elasticsearch node.
When adapting an existing session customization, keep its route and lifetime with that node. Also track any node discovery that changes the destination host.
Record client version, node class, configured service address, selected destination, proxy endpoint and exception stage. That distinguishes an obsolete hook from a later proxy rejection or Elasticsearch response.