Companion code for the article "Five silent minutes: the proxy hang my request timeout never saw".
With got-scraping, timeout.request does not end an HTTPS request while an HTTP proxy sits on an unanswered
CONNECT. With default settings the hang is in the header generator's protocol check, which runs before got
creates the request. With the header generator off, got's timer destroys a request that has no socket yet, and no
error is ever emitted. Everything here
runs on 127.0.0.1, and nothing leaves your machine.