spring-cloud / spring-cloud/spring-cloud-gateway
BUG: GRPCResponseHeadersFilter drops grpc-status-details-bin on trailers-only responses
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Describe the bug
SCG drops grpc-status-details-bin for trailers-only (immediate error) responses.
In that case GRPCResponseHeadersFilter moves only grpc-status/grpc-message into the trailer. But grpc-status-details-bin is also Trailer metadata per the gRPC HTTP/2 protocol, so it's lost and the client gets an error with no details. (The deferred case is fine via trailer passthrough.)
Version
5.0.2
ref.: https://github.com/spring-cloud/spring-cloud-gateway/issues/3783
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with GRPCResponseHeadersFilter and compare its trailers-only handling with the deferred trailer passthrough described in the issue. Use the gRPC HTTP/2 protocol reference to confirm the metadata behavior, then verify that a trailers-only immediate error preserves grpc-status-details-bin along with the other error metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java, spring
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100