Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is it able to sniff connections established before grpcudmp launch? #8

Open
jizhilong opened this issue Mar 18, 2021 · 2 comments
Open

Comments

@jizhilong
Copy link

Hi dear maintainer,
My experiment shows the following 2 cases:

  1. launch grpcdump, then launch a grpc client and invoke a grpc call -> The request/response is dumped to the console.
  2. launch a grpc client and invoking grpc calls(unary call) regularly, then launch grpcdump -> No request/response is dumped to the console.

so the question in this issue title arises. If the answer is negative, is it possible to support sniff established connections in the future?

@jizhilong
Copy link
Author

After some digging into grpcdump and gopacket, I realized the main blocker is hpack-as headers in HTTP2 are compressed with hpack, it's not possible to sniff their actual content if we skip the initial requests in which the compression tables were established.

@jschwinger233
Copy link

I've written my version of grpcdump to workaround this issue, have a try: https://github.com/jschwinger233/grpcdump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants