Files
zeekay c01e5afcae refactor: own the module path (github.com/hanzoai/grpc-web)
Per the standing fork rule, a hanzoai fork declares its OWN module path and
is required directly -- never resolved via a `replace` against the upstream
path. Keeping the upstream path meant every consumer's import line carried
the upstream brand.

  module github.com/traefik/grpc-web -> module github.com/hanzoai/grpc-web

All occurrences were import paths (package self-imports plus the test
servers and the react example server). go/grpcweb -- the package Hanzo
Ingress links -- is green.
2026-07-25 12:27:26 -07:00
..
2017-03-26 18:40:14 +01:00

Go gRPC Web Wrapper

The standard gRPC-Go Server implements a ServeHTTP method and can be used as a standard http.Handler of the the Go built-in HTTP2 server.

The grpcweb package implements a wrapper around grpc.Server.ServeHTTP that exposes the server's gRPC handlers over gRPC-Web spec, thus making them callable from browsers.

The grpcwebproxy is a binary that can act as a reverse proxy for other gRPC servers (in whatever language), exposing their gRPC functionality to browsers (over HTTP2+TLS+gRPC-Web) without needing to modify their code.