grpc-ecosystem/grpc-gateway

v2.26.2 breaks grpc-websocket-proxy

Open

#5326 opened on Mar 5, 2025

View on GitHub
 (19 comments) (0 reactions) (0 assignees)Go (16,971 stars) (2,250 forks)batch import
bughelp wanted

Description

I realize https://github.com/tmc/grpc-websocket-proxy is not officially supported by this project, but it's mentioned a lot in issues here. Just flagging that the change in #5240 breaks the websocket-proxy, causing requests to hang indefinitely.

Contributor guide

Tech stack
go
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programminggRPC conceptsHTTP/2 and websocket fundamentals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the changes introduced in pull request #5240 (referenced in the issue) that likely caused the regression. Focus on the gRPC gateway's handling of websocket upgrades and the interaction with the grpc websocket proxy. Review the relevant source files in the gateway's HTTP handler and marshaler logic to identify why requests hang indefinitely after the change.