WebSockets, SSE and HTTP/2

The proxy passes WebSockets and streamed answers. It always uses HTTP/1.1 with your app.

A client can use HTTP/2 with the proxy. The proxy always uses HTTP/1.1 with your app.

1 / 4

What goes through the proxy

Traffic	Through the proxy
WebSockets and other HTTP/1.1 upgrades	Yes. The proxy makes a tunnel to your app.
`h2c` upgrades	No. The proxy sends those requests as plain HTTP/1.1.
Server-Sent Events and streamed answers	Yes. The timeouts of the proxy never cut an answer in progress.
HTTP/2 from clients	Yes: with TLS, and in cleartext with prior knowledge.
gRPC and other protocols that need HTTP/2 end to end	No.

The proxy always uses HTTP/1.1 with your app. Thus gRPC does not work through the public proxy.

Call a gRPC service on the private network.

The headers that your app gets

The proxy removes the address headers that a client sends and sets its own, thus your app can trust them.

Connection limits

The proxy protects itself with limits on the number of connections and on the time that each one waits.