Wojtek Mach

@jmwilkinson Agreed. A PR would be appreciated!

For completeness, :nxdomain also shows up on IPv4/IPv6 mismatch. One example that comes to mind is talking to internal Fly service (ipv6-only) from ipv4-by-default connection.

This is great, I'll try to address this soon!

Yes, PRs appreciated! I think we should support `http_proxy` env var out of the box but also have an `:http_proxy` option that can be set with the same value. (Same...

I wonder if it is possible to expose some of these internals publicly and create a stream on top of these. Say we have a LiveView and we use Finch.async_request...

Are you able to overwrite that value eg `CI=true mix deps.get` or set ```yaml environment: CI: true ``` Or something along those lines? But if not, your patch is fine...

Another idea is to instead have: ```elixir {:ok, conn} = Mint.HTTP.connect(:https, "httpbin.org", 443) {:ok, conn, _acc = nil} = Mint.HTTP.request( conn, "GET", "/user-agent", _headers = [], _body = nil, _timeout...

Yes I can totally disregard unrelated messages and can document it as such. The only problem is they cannot be recovered. My understanding is in active mode we do selective...

Got it, thanks. Would you prefer to start with just recv_response/3 or recv_response/5 (that additionally has `acc` and `fun`) or both? In the PR we have both at the moment.

I renamed this to `Mint.HTTP.recv_response/3`, added basic docs and tests, and updated PR description accordingly.