KLklaussilveira·Nov 19, 2025Submission
Llhttp: Port of HTTP_parser to Llparse
2 points · Open discussionnodejs
llhttp
TypeScript2020–2025
nodejs / llhttp
llhttp
Port of http_parser to llparse
6Distinct people
6Mentions
0Explicit recommenders
2KGitHub stars
What to know before exploring
What it is
Port of http_parser to llparse
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2020-01-03 13:53:52 UTC to 2025-11-19 16:44:25 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
6 sourcesNo, brain fart on my part. You can use llhttp, which is pretty easy to use: https://github.com/nodejs/llhttp
In Show HN: unsafehttp – tiny web server from scratch in C, running on an orange piThose wasm blobs are Node's own llhttp https://github.com/nodejs/llhttp in wasm to speed up HTTP parsing. The project itself added as a dependency is also by Node https://github.com/nodejs/undici .
The question is totally legitimate but please assume core doesn't make "load random binary" level kind of goofs :)
In Fetch API has landed into Node.jsWhoa, I didn't know that! But yeah, it seems like https://github.com/nodejs/http-parser is based on nginx. It now uses https://github.com/nodejs/llhttp but has some of the same legacy.
On the other hand, deno's HTTP stuff is built on top of Hyper, a Rust library https://github.com/hyperium/hyper
In How to win at CORSNo, parsing HTTP/1.x is a nightmare and definitely not simple. It wasn't even particularly well defined until 2014 when the original RFCs were modernized, and even now there are bugs reported in HTTP parsers all the time.
Node.js came out in 2009, a full ten years after HTTP/1.1 (RFC 2068) and its original http-parser is rather hard to follow, doesn't conform to the RFCs for performance reasons, and is considered unmaintainable by the author of it's replacement[0]
As for parsing HTML, well go look at how Cloudflare have stumbled[1]
[0] https://github.com/nodejs/llhttp
[1] https://blog.cloudflare.com/incident-report-on-memory-leak-c...
In Show HN: Micro HTTP server in 22 lines of CA Faster HTTP Parser for Node.js
1 points · Open discussion