You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calls to a simple echo gRPC server from Postman or other gRPC clients result in an internal error. The error message is like Received RST_STREAM with code 1.
Steps to reproduce
This issue can be reproduced every time a gRPC method is called from a strict gRPC client like postman. I've capture the data packets, and found the root cause of it: 2 headers frames both have set the:status header.
Pseudo-header fields MUST NOT appear in a trailer section.
The same pseudo-header field name MUST NOT appear more than once in a field block. A field block for an HTTP request or response that contains a repeated pseudo-header field name MUST be treated as malformed (Section 8.1.1).
Apparently the current gRPC implementation does not conform to that.
First headers frame
Second headers frame
The text was updated successfully, but these errors were encountered:
lilac
changed the title
gRPC handler send headers frames with end_headers flags set twice
4.x: gRPC handler send headers frames with end_headers flags set twice
Nov 13, 2023
lilac
changed the title
4.x: gRPC handler send headers frames with end_headers flags set twice
4.x: gRPC handler send :status headers twice
Nov 13, 2023
Environment Details
Problem Description
Calls to a simple echo gRPC server from Postman or other gRPC clients result in an internal error. The error message is like
Received RST_STREAM with code 1
.Steps to reproduce
This issue can be reproduced every time a gRPC method is called from a strict gRPC client like postman. I've capture the data packets, and found the root cause of it: 2 headers frames both have set the
:status
header.Below are quoted from the http/2 standard
Apparently the current gRPC implementation does not conform to that.
First headers frame
Second headers frame
The text was updated successfully, but these errors were encountered: