Side N
Apache, Nginx and Caddy: which HTTPS web server
Which sources back which section of this article, and what its evidence base looks like.
Which sources back which section
| Section | Sources |
|---|---|
| What happened | nginx.org news and advisories; the Apache download and vulnerability pages; pkg.go.dev and Wikipedia for Caddy; Let’s Encrypt; GetMind and Tech Insider; CodeIT. |
| Timeline | Each dated event from the source named on its line. |
| The argument | The nginx, Apache and Caddy documentation; GetMind; Tech Insider; W3Techs; Let’s Encrypt. |
| What others add | Let’s Encrypt on renewal and OCSP; Kubernetes on ingress-nginx; the Caddy, Apache and nginx documentation on wildcards and private certificates. |
| Conclusion | All of the above, as in the sections. |
What the evidence base looks like
- 28Sources used on the page
- 28Read in full at their own pages
- 0Speed tests published by the three projects themselves
| Function | How many | What they are |
|---|---|---|
| Origin | 15 | The three projects’ own pages and documentation, and the Go package index. |
| Vendor | 7 | Let’s Encrypt, Kubernetes and a third-party package repository, on their own services. |
| Reporting | 4 | Two technology publications, a benchmark write-up and a usage survey. |
| Reference | 2 | Two Wikipedia articles. |
Reliable
Reliable, but with an interestWorth believing and reliableWeak on both, and used with careHonest, but thin
Worth believing