If a tutorial tells you to set verify=False so your proxy “works”, don’t. That’s the one setting in this whole topic I’d call actually dangerous, and a CONNECT proxy never needs it.
Quick refresher on why. For an https:// site your client asks the proxy to CONNECT to host:443, the proxy dials out and says 200, and from there it’s moving bytes it can’t read. Your TLS runs to the site. So the proxy knows the hostname, the port, the timing and how much went through, and that’s about it. No paths, no cookies, no page. Turn off cert checks though and anything sitting in the middle can read all of it.
Two things people trip on while testing this. SSH through an HTTP proxy usually gets a 403, since most proxies only allow CONNECT to known ports. And HTTP/3 can’t ride a classic tunnel, it’s TCP only, so you need CONNECT-UDP or your client drops back to HTTP/2 or 1.1 without saying much.
The curl -v walk-through: https://proxymint.com/http-connect-method/
Disclosure: our blog, we run a proxy service.

