Tratopedia
Side N繁中
Settings

Text size

Language

Theme

High contrast

Version

v1.230.2

The release this page was built from. It is what the service worker caches under.

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

SectionSources
What happenednginx.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.
TimelineEach dated event from the source named on its line.
The argumentThe nginx, Apache and Caddy documentation; GetMind; Tech Insider; W3Techs; Let’s Encrypt.
What others addLet’s Encrypt on renewal and OCSP; Kubernetes on ingress-nginx; the Caddy, Apache and nginx documentation on wildcards and private certificates.
ConclusionAll 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
FunctionHow manyWhat they are
Origin15The three projects’ own pages and documentation, and the Go package index.
Vendor7Let’s Encrypt, Kubernetes and a third-party package repository, on their own services.
Reporting4Two technology publications, a benchmark write-up and a usage survey.
Reference2Two Wikipedia articles.

Reliable

Reliable, but with an interestWorth believing and reliableWeak on both, and used with careHonest, but thin

Worth believing

Each point is one source used, placed by two judgements on a six-step scale. Points carry no names: the chart shows the shape of the evidence, not a verdict on any publisher.