WhereGoes

426 Upgrade Required

4xx client error

The client must switch to a newer or different protocol, such as HTTP/2 or TLS, before the server will handle the request, as named in Upgrade.

Common causes

  • Plain HTTP is disabled and only HTTPS is served.
  • A deprecated protocol version is refused.
  • The endpoint requires h2 or another upgrade.

How to fix it

  • Redirect plain HTTP to HTTPS with 301 or 308 as well as returning 426 to APIs.
  • Name the required protocol in the Upgrade header.
  • Keep a compatible fallback while old clients remain.

What it means for redirects and SEO

Protocol upgrades, such as requiring TLS or h2, block old crawlers and links. The Upgrade header names what is needed. Keep HTTP/1.1 available for compatibility.

Related codes