konsumer / konsumer/grpc-dynamic-gateway
Suggest not to forward hop-to-htop http headers to grpc
Open
- Dominant language
- JavaScript
- Stars
- 110
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
in the current code , every http header is added to grpc metadata.
While in the official grpc-gateway, only header starting with 'Grpc-Metadata-' will be mapped to gRPC metadata.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at index.js around line 229, where HTTP headers are added to gRPC metadata, and compare that behavior with the official grpc-gateway runtime/mux.go reference linked in the issue. Confirm which headers should be forwarded and verify that unrelated HTTP headers are no longer mapped to gRPC metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100