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

Fails to display response headers in case of "unexpected HTTP status code" #430

Open
frederictobiasc opened this issue Nov 8, 2023 · 0 comments

Comments

@frederictobiasc
Copy link

frederictobiasc commented Nov 8, 2023

Current behavior: grpcurl incorrectly states Response headers received: (empty) despite response headers being present in case there is an unexpected status code (like 401).
Expected behavior: grpcurl shows headers even in case there is an unexpected status code (and possibly no content).

$ grpcurl -vv -plaintext         -d '<redacted>' -H "Authorization: Bearer $TOKEN"         [::1]:8000 <redacted>

Resolved method descriptor:
<redacted>
Request metadata to send:
authorization: Bearer <redacted>
Response headers received:
(empty)

Response trailers received:
(empty)
Sent 1 request and received 0 responses
ERROR:
  Code: Unauthenticated
  Message: unexpected HTTP status code received from server: 401 (Unauthorized)

Wireshark:
headers-present

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

1 participant