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

Wrong grpc-status header #2961

Open
TWHOI opened this issue May 26, 2023 · 0 comments · May be fixed by #2973
Open

Wrong grpc-status header #2961

TWHOI opened this issue May 26, 2023 · 0 comments · May be fixed by #2973
Labels

Comments

@TWHOI
Copy link

TWHOI commented May 26, 2023

A Python grpc server (did not test with java yet) with plain text h2c:

  ...
  context.set_details("some details")
  context.set_code(grpc.StatusCode.RESOURCE_EXHAUSTED)
  return RESPONSE()

Leads to 3 frames being send in the response:

  • HEADERS, without grpc-status
  • DATA
  • HEADERS containing grpc-status 8 - RESOURCE EXHAUSTED
  • RST_STREAM

The gateway is unable to read the grpc status and adds a 0 / OK, so the client never sees the original grpc status.
The gateway should probably even close the connection if a non ok status code was received? I would assume that the server does not send that status code again. Clients seem to do that, they throw an exception.

@FliegenKLATSCH FliegenKLATSCH linked a pull request Jun 3, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants