Today at $DAYJOB I got to analyse why a #golang #http2 client would throw an error when talking to our own HTTP/2 server stack.

Turned out it was a bug in go (already fixed upstream but not in the version this client was compiled with), but understanding it helped us work around it server-side.

Things were complicated somewhat by the fact that this is all over HTTPS - #alpnpass was a great help so I could inspect the frames in #wireshark!

Much enjoyed this!


@raboof Nice! I remember having to setup a manual man in the middle attack with spoofed certs several years back so we could inspect and debug encrypted traffic. (We didn't have control over the server part.)

@dwardoric that's fun :) - in this case I was lucky enough that I could just patch the client to skip certificate validation entirely ;)

Sign in to participate in the conversation – a Fediverse instance for & by the Chaos community