Today at $DAYJOB I got to analyse why a 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 - was a great help so I could inspect the frames in !

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 ;)

· · Web · 0 · 0 · 1
Sign in to participate in the conversation

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.