Burp Suite User Forum

Login to post

Burp possibly doesn't close HTTP2 gRPC connection gracefully

skb | Last updated: Jan 11, 2023 12:49AM UTC

First of all, thank you for your great efforts to make HTTP2 available in Burp. I'm using Go gRPC example application named RouteGuide(https://github.com/grpc/grpc-go/tree/master/examples/route_guide) to check Burp can proxy HTTP2 gRPC messages. I configured burp to: - Support HTTP/2 - Default to HTTP/2 if the server supports it As a result of simple testing, I confirmed Burp seems to be able to proxy all kind of gRPC messages(unary, client/server/bidirectional streaming) and to record these messages in history. However, if Burp proxies the message, client dumps an error saying that server closed the stream without sending trailers. I guess Burp fails to close the stream gracefully (possibly failing to send trailers back to the client?). It might be I'm missing some configuration. I appreciate if you have any ideas to solve. Thank you.

Hannah, PortSwigger Agent | Last updated: Jan 11, 2023 10:12AM UTC

Hi Unfortunately, gRPC is not supported in Burp. We're also not able to send trailing headers with HTTP/2. We have an ongoing feature request for this functionality, to which we have added your +1.

Japh07 | Last updated: Jan 29, 2023 11:31PM UTC


William | Last updated: Mar 16, 2023 09:50PM UTC


Hannah, PortSwigger Agent | Last updated: Mar 17, 2023 09:47AM UTC

Thnks for the feedback, we've added your +1's to the ongoing feature request.

You need to Log in to post a reply. Or register here, for free.