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.

Web Servers · HTTPS · Information Security · Web Infrastructure · Comparison BriefVersions and figures as of 27 October 2026

Three servers, one job: hold the certificate and speak TLS

Apache, Nginx and Caddy: which HTTPS web server

A web server that speaks HTTPS has to hold a certificate, negotiate TLS and pass requests on to the site behind it. Apache, Nginx and Caddy all do this well, but differently. Caddy gets and renews certificates by itself and turns HTTP/3 on by default. Nginx is the fastest and lightest of the three, though its HTTP/3 is still marked experimental. Apache has no official HTTP/3, but its per-folder configuration and its modules keep it at the centre of shared hosting. Meanwhile the ground is moving: Let’s Encrypt certificates are getting shorter and its OCSP service is gone.

Three releases, a round of fixes, and shorter certificates October 2026, graded by how far each item is established

  • 1.30.6Nginx stable, 14 October 2026, fixing five flaws; mainline 1.31.8 followed on 21 October
  • 2.4.69Apache, 1 October 2026, fixing 20 CVEs
  • 2.11.7Caddy, 3 October 2026
  • 64 daysDefault Let’s Encrypt lifetime from 10 February 2027, down from 90

Confirmed

The three releases and their fixes come from each project’s own pages. nginx.org rates all five October flaws “medium”; one lets a forged TLS session skip a client-certificate check when session tickets are used. The certificate timetable and the end of OCSP come from Let’s Encrypt.

Reported by third parties

Speed and memory figures come from GetMind’s own test and from Tech Insider, not from the projects.

Not in official releases

HTTP/3 for Apache. A third-party repository, CodeIT, packages an experimental mod_http3, but it needs a patch to Apache that had not been merged upstream when CodeIT wrote on 8 October 2026.

From Caddy’s first release to 45-day certificates Dates as each source gives them; the last three are scheduled

  1. 28 Apr 2015Caddy’s first release; it has issued certificates automatically since it was feasible that year (Wikipedia; Caddy).
  2. 5 Dec 2024Let’s Encrypt announces it will end OCSP (Let’s Encrypt).
  3. 7 May 2025OCSP URLs are dropped from its certificates (Let’s Encrypt).
  4. 6 Aug 2025Its OCSP responders are turned off (Let’s Encrypt).
  5. 11 Sep 2025Native ACME support comes to Nginx as a module written in Rust (Let’s Encrypt).
  6. 11 Nov 2025Kubernetes announces that the community ingress-nginx controller will retire, with no fixes after March 2026 (Kubernetes).
  7. 2 Dec 2025Let’s Encrypt says its 90-day certificates will be cut to 45 days by 2028 (Let’s Encrypt).
  8. 20 Mar 2026Ingress2Gateway 1.0 is released to help clusters move to Gateway API (Kubernetes).
  9. Apr 2026Nginx 1.30 becomes the stable branch, adding sticky sessions and ECH and keeping upstream connections alive by default (nginx; Help Net Security).
  10. 13 May 2026Let’s Encrypt’s opt-in tlsserver profile starts issuing 45-day certificates (Let’s Encrypt).
  11. 1 Oct 2026Apache 2.4.69 is released (Apache).
  12. 3 Oct 2026Caddy 2.11.7 is released (Wikipedia).
  13. 14 Oct 2026Nginx 1.30.6 and 1.31.7 fix five vulnerabilities (nginx).
  14. 10 Feb 2027Scheduled: the default classic profile moves to 64-day certificates (Let’s Encrypt).
  15. 16 Feb 2028Scheduled: the classic profile moves to 45 days (Let’s Encrypt).
  16. 15 Mar 2029Scheduled: industry rules cap certificate lifetimes at 47 days (Let’s Encrypt).

Caddy for simplicity, Nginx for scale, Apache for compatibility What the projects’ own documents support, and what complicates it

All three now default to sound TLS, but they get there differently. Nginx has used TLS 1.2 and 1.3 by default since 1.27.3, and Caddy’s protocols run from TLS 1.2 to 1.3. Apache’s mod_ssl defaults to SSLProtocol all -SSLv3, so what is actually enabled depends on the OpenSSL underneath, and it is safer to name the versions outright. The real differences lie around TLS. Caddy obtains and renews certificates, redirects HTTP to HTTPS, and serves HTTP/3 without being asked. Nginx can do the first through its ACME module, though not for wildcard names, and nginx.org still calls its HTTP/3 module “experimental”. Apache’s mod_md handles ACME but is labelled experimental, and for wildcard names its documentation says Apache “cannot do that on its own”. None of the three adds the HSTS header for you.

  • ~2×Nginx’s lead over Caddy on static files in GetMind’s test
  • ~30%Its lead as a reverse proxy, where the app behind usually sets the pace
  • 45 daysLet’s Encrypt’s default lifetime from 16 February 2028

What complicates it

Speed rankings come from third parties, and they are not unanimous. GetMind found Nginx about twice as fast on static files and about 30% faster as a proxy. Tech Insider reports Caddy ahead by 23% with HTTP/3 on, and Nginx using about a quarter of Caddy’s memory at 10,000 idle connections, 89 MB against 340 MB. For most sites, as GetMind puts it, the difference does not matter, because both handle far more requests than a normal site will see. And the market is no longer a two-horse race: on 27 October 2026 W3Techs counted Cloudflare’s own server on 32.9% of sites, ahead of Nginx on 30.1%.

Certificates, OCSP and Kubernetes Each item as the named source gives it

QuestionWhat the record showsSource
How should renewal work now?Let’s Encrypt recommends ACME Renewal Information (ARI), which tells a client when to renew. A fixed renewal schedule written for 90-day certificates will stop fitting as lifetimes shrink.Let’s Encrypt
Is OCSP stapling still worth turning on?Not for Let’s Encrypt certificates. Their OCSP URLs were removed on 7 May 2025 and the responders turned off on 6 August 2025, so there is nothing to staple. That conclusion is ours, drawn from those dates.Let’s Encrypt
What about Nginx on Kubernetes?The community ingress-nginx controller retired after March 2026, with “no further releases, no bugfixes, and no updates to resolve any security vulnerabilities”. Kubernetes points users to Gateway API, and Ingress2Gateway 1.0 helps convert. Nginx itself is unaffected.Kubernetes
  • Wildcards

    Wildcard certificates need DNS

    Caddy; Apache; nginx

    • Caddy needs a build that includes a DNS provider module.
    • Apache’s mod_md needs a script you supply to update DNS.
    • Nginx’s ACME module does not support wildcards, so a separate ACME client is used.
  • Internal sites

    Private certificates

    Caddy; Apache

    • Caddy’s tls internal issues certificates from its own local CA.
    • Apache’s mod_md can point at your own ACME server instead of Let’s Encrypt.

Which server suits which site Each card: who it is for, its strongest point, and the trade-off

  • Caddy

    Small and medium sites, home labs, teams without an operations person

    Version 2.11.7

    • Best at: HTTPS that runs itself, with certificates, redirects and HTTP/3 on by default.
    • Trade-off: more memory and less raw speed than Nginx under heavy load.
  • Nginx

    Busy sites, load balancers, reverse proxies in front of many apps

    Stable 1.30.6

    • Best at: the highest throughput and lowest memory use of the three.
    • Trade-off: HTTP/3 is still experimental, and certificates usually need a separate tool.
  • Apache

    Shared hosting, older PHP applications, setups built on Apache modules

    Version 2.4.69

    • Best at: per-folder .htaccess files and the largest library of modules.
    • Trade-off: no official HTTP/3, so put Nginx, Caddy or a CDN in front for it.
  • Upgrade this month. Nginx to 1.30.6 or later, Apache to 2.4.69, Caddy to 2.11.7.
  • Automate renewal with ARI, and watch expiry dates. A fixed schedule will break as lifetimes shrink.
  • Add HSTS yourself, and drop OCSP stapling for Let’s Encrypt certificates.

Quick notes

  1. HTTPS web servers · 27 October 2026

    Apache, Nginx and Caddy compared

    A plain-English guide to choosing an HTTPS web server, for beginners and professionals.

    Apache, Nginx and Caddy · HTTPS web servers1 / 15

  2. The basics

    How HTTPS works in three steps

    The web server’s job: hold the certificate, speak TLS and pass requests to your site.

    1 · Connect

    The browser contacts the server on port 443 and agrees which TLS version to use.

    2 · Prove

    The server shows a certificate that proves it owns the domain name.

    3 · Encrypt

    Both sides create shared keys, and everything after that is encrypted.

    Apache, Nginx and Caddy · HTTPS web servers2 / 15

  3. The basics

    Six terms you will meet

    TermMeaning
    TLSThe encryption protocol behind HTTPS. Use versions 1.2 and 1.3 only.
    CertificateA signed file that proves a server owns its domain name.
    ACMEThe standard that lets software request and renew certificates automatically.
    HSTSA header that tells browsers to always use HTTPS for your site.
    HTTP/2Faster loading by sending many requests over one connection.
    HTTP/3HTTP over QUIC and UDP, with quicker setup on poor networks.

    Apache, Nginx and Caddy · HTTPS web servers3 / 15

  4. The three servers

    Meet the three servers

    Shares from W3Techs, 27 October 2026.

    ServerVersionIn one lineShare of websites
    Apache2.4.69 · 1 Oct 2026The most compatible: per-folder .htaccess and a huge module library21.2%
    Nginx1.30.6 · 14 Oct 2026The fastest: built for heavy traffic and for sitting in front of other apps30.1%
    Caddy2.11.7 · 3 Oct 2026The simplest: HTTPS certificates are handled for you1.2%

    Apache, Nginx and Caddy · HTTPS web servers4 / 15

  5. The short answer

    Caddy for simplicity. Nginx for scale. Apache for compatibility.

    The next slides explain why, then compare TLS, certificates and speed.

    Apache, Nginx and Caddy · HTTPS web servers5 / 15

  6. Caddy

    Caddy: automatic HTTPS

    Best for: small and medium sites, home labs and teams without an operations person.

    Strengths

    Certificates are requested, installed and renewed on their own.

    • HTTP/3 is on by default, with TLS 1.2 and 1.3.
    • A short, readable Caddyfile, with HTTP redirected to HTTPS for you.

    Watch out for

    More memory use, and lower speed than Nginx under heavy load.

    • Wildcard certificates need a custom build with a DNS module.
    • You still add the HSTS header yourself.

    Apache, Nginx and Caddy · HTTPS web servers6 / 15

  7. Nginx

    Nginx: built for scale

    Best for: high-traffic sites, load balancing and reverse proxies in front of many apps.

    Strengths

    The highest throughput and lowest memory use of the three.

    • Mature load balancing, rate limiting and TCP and UDP proxying.
    • Stable 1.30 adds ECH and sticky sessions.

    Watch out for

    HTTP/3 is still marked experimental by the project.

    • Certificates need a separate ACME client, or the newer nginx-acme module, which cannot do wildcards.
    • Upgrade to 1.30.6 or later: five flaws, all rated medium, were fixed on 14 October 2026.

    Apache, Nginx and Caddy · HTTPS web servers7 / 15

  8. Apache

    Apache: built for compatibility

    Best for: shared hosting, older PHP applications and setups that rely on Apache modules.

    Strengths

    Per-folder .htaccess files, ideal for shared hosting.

    • The largest module library, including mod_rewrite and mod_security.
    • Built-in mod_md can request and renew certificates over ACME.

    Watch out for

    No official HTTP/3. Put Nginx, Caddy or a CDN in front for it.

    • A third-party mod_http3 exists, but it needs an Apache patch not yet merged upstream.
    • mod_md is still labelled experimental, and wildcards need a DNS script.

    Apache, Nginx and Caddy · HTTPS web servers8 / 15

  9. Comparison

    TLS defaults and HTTP/3 support

    ApacheNginxCaddy
    TLS versionsDepends on OpenSSL; set it yourself1.2 and 1.3 since 1.27.31.2 and 1.3
    HTTP/2Yes, with mod_http2Yes, with http2 on;Yes, on by default
    HTTP/3Not in official releasesYes, marked experimentalYes, on by default
    HSTS headerYou add itYou add itYou add it

    Apache, Nginx and Caddy · HTTPS web servers9 / 15

  10. Comparison

    Getting certificates automatically

    Automatic certificatesWildcard certificatesInternal CA
    ApacheYes: mod_md, or an external ACME clientA DNS scriptPoint mod_md at your own ACME server
    NginxAn ACME client, or the nginx-acme moduleAn external ACME client only (DNS-01)An internal ACME CA plus a client
    CaddyYes: built in, on by defaultBuild with a DNS moduleYes: tls internal

    Apache, Nginx and Caddy · HTTPS web servers10 / 15

  11. Comparison

    Certificate lifetimes are getting shorter

    • 90 daysLet’s Encrypt’s default lifetime today
    • 64 daysThe default from 10 February 2027
    • 45 daysThe default from 16 February 2028
    • What to do: use an ACME client that supports ARI, and monitor expiry dates. A fixed “renew every 60 days” schedule will stop working.

    Apache, Nginx and Caddy · HTTPS web servers11 / 15

  12. Comparison

    Speed: Nginx leads, most of all on static files

    Source: GetMind’s own test, September 2026. Indicative only; test your own setup.

    TestNginxCaddy
    Static files, requests per secondabout 142,000about 70,000
    Reverse proxy, requests per secondabout 43,500about 33,600

    Apache, Nginx and Caddy · HTTPS web servers12 / 15

  13. Sample setup

    A complete HTTPS site in a few lines of Caddyfile

    HTTP-to-HTTPS redirects and HTTP/2 and HTTP/3 come on without a line. Nginx needs a longer file plus a certificate tool; Apache needs mod_md directives or an external client.

    LineWhat it does
    example.com, www.example.comNames the site; Caddy gets and renews its certificate
    encode zstd gzipCompresses responses
    header Strict-Transport-Security max-age=63072000Adds HSTS for two years
    reverse_proxy 127.0.0.1:3000Passes requests to your app on port 3000

    Apache, Nginx and Caddy · HTTPS web servers13 / 15

  14. Checklist

    Four things to check this month

    Upgrade

    Nginx 1.30.6 or later, Apache 2.4.69 and Caddy 2.11.7.

    Drop OCSP stapling

    Let’s Encrypt turned off its OCSP responders in August 2025, so stapling no longer helps with its certificates.

    Automate renewal

    Use an ACME client that supports ARI, and monitor expiry dates.

    Leave ingress-nginx

    The community Kubernetes controller retired in March 2026. Move to Gateway API.

    Apache, Nginx and Caddy · HTTPS web servers14 / 15

  15. Decision

    Which one should you choose?

    Your situationPickWhy
    Personal site or home labCaddyAutomatic HTTPS and almost no upkeep
    Busy site or load balancerNginxHighest speed and lowest memory use
    Shared hosting or older PHPApache.htaccess and existing modules
    KubernetesGateway APIThe community ingress-nginx controller is retired

    Apache, Nginx and Caddy · HTTPS web servers15 / 15

  • nginx.org, news, security advisories, “Configuring HTTPS servers”, ngx_http_v3_module, ngx_http_acme_module and Changes with nginx 1.30
  • Help Net Security, “What changed in nginx 1.30.0”, 15 Apr 2026
  • Apache HTTP Server Project, download page, 2.4 vulnerabilities, mod_md, mod_ssl and event MPM
  • pkg.go.dev, caddyserver/caddy/v2
  • Wikipedia, “Caddy (web server)” and “Nginx”
  • Caddy documentation, Automatic HTTPS, tls directive and global options
  • Matthew McPherrin, “Decreasing Certificate Lifetimes to 45 Days”, Let’s Encrypt, 2 Dec 2025
  • Let’s Encrypt, “Certificate Lifetime Rationale and Plans”
  • Josh Aas, “Ending OCSP Support in 2025”, 5 Dec 2024
  • Josh Aas, “Native ACME Support Comes to NGINX”, 11 Sep 2025
  • Tabitha Sable, “Ingress NGINX Retirement: What You Need to Know”, Kubernetes, 11 Nov 2025
  • Beka Modebadze and Steven Jin, “Announcing Ingress2Gateway 1.0”, Kubernetes, 20 Mar 2026
  • W3Techs, web server usage, 27 Oct 2026
  • Fabian Budde, “Caddy vs Nginx: Benchmarks and Real-World Use With 139 Sites”, GetMind, 26 Sep 2026
  • Sofia Lindström, “Caddy vs Nginx 2026”, Tech Insider, 30 Apr 2026
  • CodeIT, “Apache HTTP/3 Is Live”, 8 Oct 2026. All read 27 Oct 2026.

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.

Versions

This document is rewritten when what it says has to change. Every version stays published at its own address.

  1. v0001 current

The current version is also at latest/.