Go and enhance your calm: demolishing an HTTP/2 interop problem

It seems to be an upstream problem within Go?

Should Go not resolve this issue instead of asking everybody to workaround the issue and reading the body response and creating this over complicated defer function?....