Caddy VS Apache

No, look at the associated unit test: https://github.com/caddyserver/caddy/blob/c6eb186064091c79f4...

If that test fails we could serve PHP source code instead of having it be evaluated, a major security flaw.

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 think that recompiling with upgraded Go will not solve the issue. It seems Caddy imports `golang.org/x/net/http2` and pins it to v0.22.0 which is vulnerable: https://github.com/caddyserver/caddy/issues/6219#issuecommen....

Caddy [1] is a single binary. It is not minimal, but the size difference is barely noticeable.

serve also comes to mind. If you have node installed, `npx serve .` does exactly that.

There are a few go projects that fit your description, none of them very popular, probably because they end up being a 20-line wrapper around http frameworks just like this one.

[1] https://caddyserver.com/

Each app’s front end is built with Qwik and uses Tailwind for styling. The server-side is powered by Qwik City (Qwik’s official meta-framework) and runs on Node.js hosted on a shared Linode VPS. The apps also use PM2 for process management and Caddy as a reverse proxy and SSL provisioner. The data is stored in a PostgreSQL database that also runs on a shared Linode VPS. The apps interact with the database using Drizzle, an Object-Relational Mapper (ORM) for JavaScript. The entire infrastructure for both apps is managed with Terraform using the Terraform Linode provider, which was new to me, but made provisioning and destroying infrastructure really fast and easy (once I learned how it all worked).

So I dug a little deeper and came across this gem: Caddy. Caddy is this fantastic, extensible, cross-platform, open-source web server that's written in Go. The best part? It comes with automatic HTTPS. It basically condenses all the work our scripts and manual maintenance were doing into just 4-5 lines of config. So, stick around and I'll walk you through how to set up an automatic SSL solution with Caddy, Docker and a Node.js server.

Let's use Caddy which can act as reverse-proxy with automatic HTTPS coverage.

Even if it may be simple, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632

I personally would make the trade off of taking on more complexity so that I can have extra compatibility.

One of the most heavily used Russian software projects on the internet https://www.nginx.com/blog/do-svidaniya-igor-thank-you-for-n... but it's only marginally more modern than Apache httpd.

In light of recently announced nginx memory-safety vulnerabilities I'd suggest migrating to Caddy https://caddyserver.com/

Single-page applications (SPAs) existed before S3, but given that you still had to set up, scale, and maintain servers using something like Apache or NGINX in order to serve them, the advantages for “Ops” or “DevOps” were not so different to running a “real server” with a language like PHP, python, or Java.

Apache(prefork mode) + mod_php.

Simiplicity is nice, but there are reasons why Perl and PHP were the popular choices for web stacks in the early 2000's--they are faster and easier to develop with than C and likely safer than C too.

mod_perl (https://perl.apache.org/) and mod_php (https://cwiki.apache.org/confluence/plugins/servlet/mobile?c...) helped to make Apache httpd (https://httpd.apache.org/) the number one web server in the early days of the web.

https://httpd.apache.org/ - Apache2 website

The Apache HTTP Server project was initially launched in 1995 by a group of web developers and administrators who sought to improve upon the existing web server software available at the time. The project has since evolved into a collaborative effort, with contributors from around the world working together to maintain and enhance the server. Today, the Apache HTTP Server is managed by the Apache Software Foundation, a non-profit organization that oversees the development of numerous open source software projects.

Apache websites of friends and acquaintances

Apache: This is the web server that is used in the LAMP stack. Apache is an open-source web server that provides a flexible and scalable platform for hosting web applications.

Install the web server software: Download the appropriate version of Apache HTTP Server for your operating system from the official website (https://httpd.apache.org/). Follow the installation instructions provided in the documentation.

Popular web servers include Apache and Nginx. Apache is the most widely used web server on the internet, and it is known for its flexibility and extensibility. Nginx, on the other hand, is known for its speed and efficiency, and it is often used as a reverse proxy or load balancer.