Should grpc-web be served on the HTTP port or on a separate port?

[amaury1093]

Summary

Bind grpc-web to the existing HTTP.

Problem Definition

Right now, grpc-web is serving on a different port than the HTTP server: #8077 (comment). But is it useful to expose an additional port?

Proposal

1. Keep grpc-web on a separate port (status quo)

Advantages:

• clarity: one endpoint for gRPC, another endpoint for grpc-gateway (HTTP), and another one for grpc-web

2. Serve grpc-web under the same port as HTTP

grpc-web has a `` function to filter grpc-web requests. Our HTTP server can check if an incoming request is grpc-web, if yes, handle it, if not, fallback to what it used to do. Any example is given in this code snippet.

Advantages:

• grpc-web is really HTTP under the hood, so we don't have 2 HTTP servers.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned