Introducing end-to-end HTTP/2 support from client to origin server
Blog post from Ngrok
Ngrok has announced support for HTTP/2 end-to-end, enabling the use of HTTP/2-based protocols like gRPC through its HTTP edges, marking a significant step in enhancing online speed, efficiency, and security. HTTP/2, introduced in 2015, improves web content delivery by utilizing binary encoding, multiplexing, header compression, and stream prioritization, collectively reducing latency and increasing performance. Ngrok's platform historically defaulted to HTTP/1.1, but now supports direct negotiation for HTTP/2, allowing developers to specify their desired protocol. The implementation includes robust security features and leverages HTTP/2 Cleartext for non-encrypted connections, while TLS is used to enhance security during client-server negotiation via Application Layer Protocol Negotiation (ALPN). The support for HTTP/2 lays the groundwork for future expansions, such as ALPN and Connection Upgrade negotiation methods, and the potential to support higher-level protocols like gRPC, thus broadening the capabilities of ngrok's platform.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Developer Experience | 1 | 373 | 169 | 92 | +54% |
| Real-time | 1 | 2,723 | 657 | 208 | +15% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.