Mirror of forum.nim-lang.org

7096 :: Which HTTP server library?

• mildred (orginal) [2020-11-15T21:56:57+01:00] view original

  Hello,

  For my nimnews package, I wanted to know what were the best HTTP server library options I had. For the moment, I'm using Jester but I'm not making use of the framework part at all as I prefer to split my code in procedure and not having to write all by handlers in the same place.

  For the moment, I use Jester with things like this:

  proc root*(req: Request): Future[ResponseData] {.async.} =
    block route:
      redirect("/group/")
  Run

  Unfortunately this breaks in newer Jester 1.4.0 because redirect expects to be called from a context it does not have. See https://github.com/dom96/jester/issues/269.

  I wanted to know what HTTP server there was out there with a rather complete implementation (I remember using the standard library server and it was missing code around parameter handling). I would need async support too.

  Thank you for your ideas.

---

• spip (orginal) [2020-11-16T00:38:21+01:00] view original

  You could start looking there and then extend your search to Nimble packages...

---

• mildred (orginal) [2020-11-16T09:34:31+01:00] view original

  Looking at https://nimble.directory/search?query=http there are plenty of packages, but it seems only a limited number are web server libraries:

  • httpkit: does not even manages the transport layer
  • microasynchttpserver: does not seems featureful enough (cookies, form-data, ...)
  • httpbeast
  • httpx (based on httpbeast it seems)
  • zfblast: supports websockets, its feature set should be decent
  • whip: based on httpbeast too
  • zfcore: only a framework based on zfblast
  • nimplehttpserver

  I was looking for people who used or wrote those libraries to get some feedbacks about them.

---

• jackhftang (orginal) [2020-11-16T10:55:48+01:00] view original

   wanted to know what HTTP server there was out there with a rather complete implementation
  Run

  Prologue should be a rather complete implementation of a HTTP server and the most featureful one written in Nim AFAIK.

---

• enthus1ast (orginal) [2020-11-16T11:09:31+01:00] view original

  And here is an example of a complete app that uses prologue: https://github.com/enthus1ast/nimNopaste/blob/master/src/nopaste.nim

---

• GULPF (orginal) [2020-11-16T11:13:00+01:00] view original

  I've been moving a small project from Jester to Prologue due to the missing middleware support in Jester and I really like it so far. The documentation is excellent and unlike Jester it doesn't rely heavily on macros.

---

• Allin (orginal) [2020-11-19T15:36:55+01:00] view original

  hello,

  If you have special requirements with HTTP parameter handling (https://www.iana.org/assignments/http-parameters/http-parameters.xhtml) I recommend you use a reverse proxy (it will also bring HTTP/2, security, buffering, TLS certificates, and more...). Myself, I used to use nginx, but have converted to Caddy (https://caddyserver.com/) lately.

  If by HTTP parameters you mean HTML query parameters, they are not part of HTTP spec and therefore out of scope for HTTP servers. However, I just pushed bindings for uriparser to GitHub, so you can use it with any server: https://github.com/olliNiinivaara/uriparser-nimbinding

  If async requirement is not a sine qua non for you, I suggest you to check out GuildenStern, too.

---