h2o
quiche
h2o | quiche | |
---|---|---|
12 | 26 | |
10,721 | 8,928 | |
0.2% | 1.3% | |
9.8 | 9.0 | |
11 days ago | 2 days ago | |
C | Rust | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
h2o
-
Nghttp3 1.0.0 – HTTP/3 library written in C
It's constantly updated: https://github.com/h2o/h2o/commits/master
- Fastly 0day: Malformed HTTP/1.1 Request Causes out of Memory Error Within H2O Server
- Malformed HTTP/1.1 Request Cause of of Memory Error Within H2O Server (Zero Day)
-
What happens if you put HTTP server inside Postgres?
In the past weeks, I've taken the task of adding an embedded HTTP server to Omnigres. Since Omnigres is implemented in C , it was only natural for me to choose libh2o to implement the functionality of an HTTP server. It did help that H2O is known for its good performance characteristics.
-
35M Hot Dogs: Benchmarking Caddy vs. Nginx
h2o [1] was excellent when I tried it for TLS termination. And it got http/2 priorities right. It's a shame they don't make regular releases.
1. https://github.com/h2o/h2o/
-
C++ (or C, I guess) application server that's QUIC/HTTP3 ready?
libh2o is probably your friend https://github.com/h2o/h2o
- H2O - the optimized HTTP/1, HTTP/2, HTTP/3 server
-
Damn callbacks
Also make sure you hydrate your server properly as well.
-
Nginx is now the most popular web server, overtaking Apache
How about H2O? It's supposed to be significantly faster than Nginx: https://h2o.examp1e.net/
quiche
-
Nghttp3 1.0.0 – HTTP/3 library written in C
The title of this post puts emphasis on "written in C", making me wonder when this would ever be a desirable feature, given that more secure implementations are available, and can be integrated into old C projects just as easily.
No need to rewrite everything from the ground up: https://github.com/cloudflare/quiche#curl
-
Curl HTTP/3 with quiche discouraged
The issue is dead silent too!
https://github.com/cloudflare/quiche/issues/1115
- Best performing quic implementation?
-
Oxy is Cloudflare's Rust-based next generation proxy framework
Even though Oxy is a proprietary project, we try to give back some love to the open-source community without which the project wouldn’t be possible by open-sourcing some of the building blocks such as https://github.com/cloudflare/boring and https://github.com/cloudflare/quiche.
-
How Rust and Wasm power Cloudflare's 1.1.1.1
They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun
-
What is a CDN? How do CDNs work?
It's more like Cloudflare forked nginx a long time ago, and is meanwhile in the very slow (like, decade-long) process of replacing it entirely.
The Cloudflare Workers Runtime, for instance, is built directly around V8; it does not use nginx or any other existing web server stack. Many new features of Cloudflare are in turn built on Workers, and much of the old stack build on nginx is gradually being migrated to Workers. https://workers.dev https://github.com/cloudflare/workerd
In another part of the stack, there is Pingora, another built-from-scratch web server focused on high-performance proxying and caching: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...
Even when using nginx, Cloudflare has rewritten or added big chunks of code, such as implementing HTTP/3: https://github.com/cloudflare/quiche And of course there is a ton of business logic written in Lua on top of that nginx base.
Though arguably, Cloudflare's biggest piece of magic is the layer 3 network. It's so magical that people don't even think about it, it just works. Seamlessly balancing traffic across hundreds of locations without even varying IP addresses is, well, not easy.
I could go on... automatic SSL provisioning? DDoS protection? etc. These aren't nginx features.
So while Cloudflare may have gotten started being more-or-less nginx-as-a-service I don't think you can really call it that anymore.
(I'm the tech lead for Cloudflare Workers.)
- Using WebTransport
-
Is it better to learn web development with Python or C?
Ask Cloudflare why they use HTTP/3 and QUIC https://github.com/cloudflare/quiche.
- DNS-over-HTTP/3 in Android
-
The MQTT broker powering Cloudflare's new Pub/Sub product is written in Rust!
Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.
What are some alternatives?
Proxygen - A collection of C++ HTTP libraries including an easy to use HTTP server.
quinn - Async-friendly QUIC implementation in Rust
haproxy - HAProxy Load Balancer's development branch (mirror of git.haproxy.org)
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
nginx-adapter - Run Caddy with your NGINX config
quic-go - A QUIC implementation in pure Go
urbit - An operating function
shadowsocks-rust - A Rust port of shadowsocks
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
neqo - Neqo, an implementation of QUIC in Rust
Folly - An open-source C++ library developed and used at Facebook.
s2n-quic - An implementation of the IETF QUIC protocol