Skip to content
Cloudflare Docs

HTTP/2

HTTP/2 uses the TCP transport protocol and TLS to secure communications and improves page load times.

Availability

Section titled “Availability”
Free Pro Business Enterprise

Availability

Yes

Yes

Yes

Yes

Can customize

No

Yes

Yes

Yes

Enable HTTP/2

Section titled “Enable HTTP/2”

HTTP/2 is enabled by default for all plans (though it does require an SSL certificate at Cloudflare’s edge network).

Disable HTTP/2

Section titled “Disable HTTP/2”

Domains on Free plans cannot disable Cloudflare's HTTP/2 setting.

To disable HTTP/2 in the dashboard:

  1. Log into the Cloudflare dashboard ↗.
  2. Select your account and zone.
  3. Go to Speed > Optimization.
  4. Go to Protocol Optimization.
  5. For HTTP/2, switch the toggle to Off.

ERR_HTTP2_PROTOCOL_ERROR

Section titled “ERR_HTTP2_PROTOCOL_ERROR”

Requests proxied by Cloudflare may result in an error for visitors with the error code ERR_HTTP2_PROTOCOL_ERROR visible in the Developer Tools Console. These errors are usually due to an issue on the origin web server configuration, but might only materialize when requests are proxied by Cloudflare depending on the client browser's behavior. Some possible causes are:

Malformed HTTP response headers

Section titled “Malformed HTTP response headers”

The origin web server may be sending improperly formatted HTTP response headers.

Resolution

Section titled “Resolution”

Make a request directly to your origin web server and inspect its HTTP response headers for anomalies. Make sure that the field values respect the following requirements:

Compression issues

Section titled “Compression issues”

Examples of compression issues include the origin web server serving gzip encoded compressed content but failing to update the Content-Length header, or the origin web server serving broken gzip compressed content.

Resolution

Section titled “Resolution”

You can try to disable compression at your origin web server and rely on Cloudflare to compress content.

You can also review your origin server's compression settings to make sure the compression is working as expected.