DAdaurnimator·Sep 9, 2024
In LuaJIT PR: Add Support for RISC-V 64daurnimator
lua-http
Lua2017–2024
daurnimator / lua-http
lua-http
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0; client and server.
2Distinct people
5Mentions
0Explicit recommenders
876GitHub stars
What to know before exploring
What it is
HTTP Library for Lua. Supports HTTP(S) 1.0, 1.1 and 2.0; client and server.
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 year5 dated mentions
Observed mentions: 2017-02-22 23:16:09 UTC to 2024-09-09 13:49: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 |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 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 | 1 | 0 | 1 |
What Hacker News says
5 sourcesThis is really cool, I'd love to write frontends in Lua. For side project backend development, I've been using Apache and mod_lua[1] (Openresty is Lua for nginx[2]) for a couple of years now. In particular Lua with Luajit is such a kick ass platform, I've always wondered why it hasn't gotten more attention than it has. There are at least two high quality event loop http servers written with it [3][4] and some quite mature web application frameworks [5][6]. Really seems like the Lua backend story is set to explode.
[1] https://httpd.apache.org/docs/trunk/mod/mod_lua.html
[2] https://openresty.org/en/
[3] https://luvit.io/
[4] https://github.com/daurnimator/lua-http
[5] http://leafo.net/lapis/
[6] http://sailorproject.org/
In Fengari: Lua for the Browser> However every existing implementation does require it
lua-http does not. https://github.com/daurnimator/lua-http/
Though the client won't auto negotiate http2 without TLS (yet... https://github.com/daurnimator/lua-http/blob/0b54603bfc132dc...), you have to tell it to do so explicitly.
In Node.js: Initial experimental implementation of HTTP/2I use pandoc (http://pandoc.org/) to be able to write in markdown, and output to man pages.
See e.g. https://github.com/daurnimator/lua-http/blob/master/doc/Make... (and the 'doc' directory in general)
In Mdoc(7) – semantic markup language for formatting manual pagesAs the author of a http library (lua-http https://github.com/daurnimator/lua-http) that doesn't, I'm interested in how you'd want retries (not to mention exponential backoffs) to work:
- Should they be the default?
- What requests should be retried? (as much as we wish GETs were idempotent... they're not) see https://lists.w3.org/Archives/Public/ietf-http-wg/2017JanMar... for an intro to the complexities here
- What should get reused? (e.g. do new dns lookup? reuse connection? reuse proxy connection?)
- How to handle non-replayable pieces? (e.g. request bodys coming from a fifo)
- Usually a request has a timeout/deadline. should it be restarted for the retry? (probably not)
I haven't implemented retries yet, as the above questions seem hard to answer without knowing application/server specific qualities (and hence should be left to the us
Read the rest
er of the http library). Please feel free to file an issue :)