ms-jpq / golang-interview-stainless

Debug for GO

I have about 4 days of GO experience

What I Know

Alex mentioned that the bug squash involves the HTTP stack, so I have prepared my debugging environment.

Debug Stack

• openssl: Using go's environ SSL_CERT_FILE, I can inject my own CA cert for debugging HTTPS, if needed. (Linux Only)

• dnsmasq: I use dnsmasq + macOS's native /etc/resolver/* to avoid touching /etc/hosts, because it feels dirty.

• socat: Used for a simple fake HTTP(s) server.

• mitmproxy: Used for debugging HTTP(s) traffic.