gRPC-Web is a proxy protocol for accessing gRPC services from browsers, built on top of simple HTTP requests that browsers support.
Native gRPC relies on HTTP/2, and there is ongoing discussion regarding HTTP/3 support.
It’s not obvious whether gRPC-Web supports HTTP/3. Given its purpose of browser support, it works not only on HTTP/2 but also on HTTP/1.1.
There have been no protocol updates or precedents for standardization for gRPC-Web.
gRPC-Web seemingly works on HTTP/3
In reality, when a frontend proxy provides HTTP/3, gRPC-Web also operates on HTTP/3. For instance, Google’s application load balancer among its load balancer products provides HTTP/3, and when providing gRPC-Web services behind it, connections are made over HTTP/3.
The specific version of HTTP used for each connection depends on a browser. It is speculated that gRPC-Web client libraries often implement using the fetchAPI, and in the case of Chrome, it actively utilizes HTTP/3 for fetch().
Since HTTP/3 connects via Quic/UDP, performance improvements can be expected as a WAN protocol. However, this browser behavior also indicates that individual gRPC-Web services have no means of controlling the HTTP version.
Although our production clusters unintentionally ended up with gRPC-Web over HTTP/3 configurations, no issues have occurred, even including server-side streaming. We have good results of reproducing the actual configuration with our test suites, and it’s safe to say that it’s been operating stably.
gRPC-Web over HTTP/3 configuration
The functionality of the GCP load balancer automatically enables gRPC-Web to support HTTP/3, so we haven’t verified the necessary configuration. However, the load balancer only performs protocol conversion and minimal HTTP header manipulation.
For gRPC-Web proxies, Envoy is often adopted. It is presumed that by defining downstream settings for HTTP/3 in addition to the existing upstream settings, gRPC-Web can be delivered over HTTP/3. Specifically, it should suffice to configure HTTP/3 on the UDP port downstream of Envoy and advertise alt-svc on the TCP port for HTTP/2.
Chuma Takahiro
Related articles
Asterisk’s configuration consists of numerous file sets. The dial plan, routing by number, is defined in extensions.conf.
Example of a simple extension
The dial plan follows the syntax as shown below:
[internal]
exten => _1XX,1,Dial(PJSIP/${EXTEN},30)
same => n,Hangup()
The structure of a block that matches each called number is as follows:
……
gRPC-Web is a proxy protocol for accessing gRPC services from browsers, built on top of simple HTTP requests that browsers support.
Native gRPC relies on HTTP/2, and there is ongoing discussion regarding HTTP/3 support.
It’s not obvious whether gRPC-Web supports HTTP/3. Given its purpose of browser support, it works not only on HTTP/2 but also on HTTP/1.1.
……
Asterisk is the most well-known open-source VoIP server. It serves as the core for an internal telephony network with SIP softphones and can be extended to integrate with the public switched telephone network (PSTN gateways) and computer telephony integration (CTI).
Preliminary knowledge
Before diving into the setup of Asterisk itself, it is effective to phase the deployment project and build it gradually. Here are the key phases:
……
Google Kubernetes Engine (GKE) can expose HTTPS services using Kubernetes Gateway/Ingress.
To expose non-HTTP services, you need to separately set up
External TCP/UDP Network Load Balancing and configure routing to the Service.
While each GKE cluster can be shared among multiple gateways, TCP load balancer needs to be added separately for each port you want to expose.
Also, even for HTTPS services, manual configuration may be necessary to utilize additional GCP features.
If you set the front end of Google Kubernetes Engine to ingress, a GCP health check will be automatically created and passed. Otherwise, the backend service will not open even if the pod is working properly.
The default health check behavior that is automatically created is to check that you can HTTP GET / and get 200OK. If the backend is implemented to handle this request, it will pass a health check.