DeepfakeHTTP VS Nginx

A new version of DeepfakeHTTP is out! I decided to add a new --dir option, allowing to host static content as static servers do. However, unlike regular static servers, DeepfakeHTTP can also host executable stuff, such as shell scripts or JavaScript. In order to have JavaScript executed on the server side you need to specify 'use server' at the beginning of the code (similar to the well-known 'use strict').

The new release of DeepfakeHTTP brings new features.

https://github.com/xnbox/DeepfakeHTTP From the README.md.

DeepfakeHTTP is a web server that uses HTTP dumps as a source for responses.

Download the latest release of df.jar

View on GitHub

When I told them that I created DeepfakeHTTP, no one really reacted. Dad said: – Son, I understand that the idea of simulating an HTTP server is interesting, but what am I going to do with this simulator you created?... Will he fix the engine from the hay mower for me, or what?! Daddy took his oil-soaked, frayed-in-time notebook, and went to assemble the engine parts. – No, Dad, my server sure can't fix your motor, I replied sadly and went to bed. At night I dreamed that I was wandering through a junkyard of old, abandoned engines and shouting: – Maybe someone needs an open source mock server, with HTTP dumps under the hood? But there was such a silence around, you could hear the tedious flapping of the wings of a butterfly slowly flying past my eyes... But the engines must have heard me and some kind of switch turned, as I woke up in the morning in a very different mood! I remembered that Dad was always looking for some kind of tool for his technical notes. He had tried Word and LibreOffice Calc and Excel... But something would drift to the side, or go into a different column, or jump to a new page when there was still enough space on this one... Anyway, the oily notebook continued to take its honorable place in Dad's workshop. No, don't get me wrong, I suggested that he do all his business in a text file, but that didn't work out either. "There's no clarity", - Dad said, I want me to put in bolts for KR-18, and all my bolts for KR-18 show up right away. And Uncle Jerry's bolts, too. And that I can see what bolts Uncle Jerry has, and he can see what I have. And that Uncle Jerry and I could both see and update, him at his house and me at mine. It became clear to me that he wanted something like ERP. I thought, what if you don't write any ERP, but simulate it. Simulate it with the hands of Dad and Uncle Jerry. So, let's get down to business! We take a text file, we call it john.txt, and we write:

Yeah, unless I'm looking at it wrong, there doesn't seem to be any meaningful difference between 1.25.5 and 1.26.0:

https://github.com/nginx/nginx/compare/release-1.25.5...rele...

However, it's very unlikely that .NET developers will directly expose their Kestrel-based web apps to the internet. Typically, we use other popular web servers like Nginx, Traefik, and Caddy to act as a reverse-proxy in front of Kestrel for various reasons:

> I actually don't understand why I am seeing arguments like this all the time.

Have a look at:

https://github.com/nginx/nginx/blob/master/src/http/modules/...

It's got the whole checklist: nginx idiosyncratic module system, inline parsing, custom utf conversion, buffer preallocation and adjustments, linked lists, comments about side effects of custom allocator, and probably other things.

It's not easy to deal with source like that and any serious improvement to that area would effectively be a rewrite anyway.

Since anything doing work in nginx is a module anyway, it wouldn't even have to be a full rewrite in one go.

According to this article, nGinx is being used to serve 34% of all websites in the world. I checked out who's contributing to nGinx, and just like I thought, the project has 8,208 commits, and 5,366 of those commits was made by 2 software developers; igorsoev and mdounin.

Nginx + Roadrunner (fcgi mode)

Apache’s mod_fastcgi’s last commit was 2 weeks ago:

https://svn.apache.org/viewvc/httpd/httpd/trunk/

It’s a fork of what you linked (and was more popular afaik back when fastcgi was state of the art, and apache was the undisputed champion of web servers).

These days, nginx has more market share than apache, and its fastcgi module is one of the more recently updated ones in its source tree (5 months vs multiple years):

https://github.com/nginx/nginx/tree/master/src/http/modules

If I was going to build an embedded web server, I’d start with nostd rust, probably with though axum + tokio, since thats already memory safe-ish.

If I needed fastcgi for some reason (dynamically loadable endpoints, or os-level isolation), there are at least four implementations of fastcgi for it. No idea if any are decent though.

APISIX is an API Gateway. It builds upon OpenResty, a Lua layer built on top of the famous nginx reverse-proxy. APISIX adds abstractions to the mix, e.g., Route, Service, Upstream, and offers a plugin-based architecture.