Jacek Sieka 34d193061e httpclient: add CONNECT proxy / tunnel support (#656) ...

Using `tunnel`, a general TCP tunnel can be created for any protocol via
a HTTP proxy. This tunnel is typically used for establishing TLS
connections via a proxy but any protocol can be used.

When a tunnel is established, the connection is removed from the session
pool and given to the caller who is now responsible for closing it.

Because the tunnel connection itself can be encrypted, we return an
`AsyncStream` that the caller must close (rather than a
`StreamTransport`).

This PR also moves DNS name resolution to the connection provider - this
has the effect of delaying DNS lookup until the actual connect attempt
is made - earlier, DNS lookups would happen when creating the HTTP
address. The move allows the proxy to perform the name resolution when
relevant - the move also prepares the API for async name resolution.

Callers can still skip name resolution by providing an explicit list of
addresses to connect to.

2026-06-16 10:20:46 +00:00

..

asyncstream.nim

httpclient: add CONNECT proxy / tunnel support (#656)

2026-06-16 10:20:46 +00:00

boundstream.nim

streams: cleanup (#649)

2026-06-01 11:57:21 +02:00

chunkstream.nim

http: align with RFC 9112, deprecate pipelining (#653)

2026-06-16 11:12:14 +02:00

tlsstream.nim

tests: more tls tests (#643)

2026-05-05 14:59:05 +00:00