diff --git a/public/__redirects b/public/__redirects index 4423a53dbcfd859..e58786e463b88a6 100644 --- a/public/__redirects +++ b/public/__redirects @@ -1182,6 +1182,7 @@ /support/more-dashboard-apps/cloudflare-apps/managing-cloudflare-apps/ /workers/ 301 /support/more-dashboard-apps/cloudflare-apps/removing-cloudflare-apps/ /workers/ 301 /support/troubleshooting/http-status-codes/http-status-codes/ /support/troubleshooting/http-status-codes/ 301 +/support/troubleshooting/cloudflare-errors/troubleshooting-other-errors/ /speed/optimization/protocol/http2/#err_http2_protocol_error 301 # r2 /r2/platform/s3-compatibility/api/ /r2/api/s3/api/ 301 diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx index 13906f7a73ace21..1bdb9d335c91536 100644 --- a/src/content/docs/speed/optimization/protocol/http2.mdx +++ b/src/content/docs/speed/optimization/protocol/http2.mdx @@ -42,3 +42,29 @@ To disable **HTTP/2** in the dashboard: To disable **HTTP/2** with the API, send a [`PATCH`](/api/resources/zones/subresources/settings/methods/edit/) request with `http2` as the setting name in the URI path, and the `value` parameter set to `"off"`. + +## 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 + +The origin web server may be sending improperly formatted HTTP response headers. + +#### 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: + +- [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5) +- [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) +- [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1) + +### 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 + +You can try to disable compression at your origin web server and rely on Cloudflare to [compress content](/speed/optimization/content/compression/). + +You can also review your origin server's compression settings to make sure the compression is working as expected. diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-other-errors.mdx b/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-other-errors.mdx deleted file mode 100644 index 87505263fa588b6..000000000000000 --- a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-other-errors.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -pcx_content_type: troubleshooting -title: Troubleshooting other errors -source: null - ---- - -Some other type of errors might be returned to visitors for proxied requests depending on the origin web server configuration. - -:::caution - - -As the root cause of these errors is not Cloudflare, this document is only designed to provide investigation avenues to help troubleshooting. - - -::: - -:::note - - -Cloudflare Support only assists the domain owner to resolve issues. If you are a site visitor, report the problem to the site owner. - - -::: - -## ERR\_HTTP2\_PROTOCOL\_ERROR - -Requests proxied by Cloudflare may result with an error for the visitors with `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. - -* A malformed HTTP response header on the origin web server. - -**Resolution**: Make a request directly to your origin web server and take a look at the HTTP response headers and see if you can see anything that looks abnormal. -Make sure that the field values are respecting the following requirements: [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#section-5.5), [RFC 9113](https://www.rfc-editor.org/rfc/rfc9113.html#section-8.2.1) and [RFC 5234](https://www.rfc-editor.org/rfc/rfc5234#appendix-B.1). - -* A compression issue, for example the origin web server is serving gzip encoded compressed content but is not updating the `content-length` header, or the origin web server is serving broken gzip compressed content. - -**Resolution**: In this case you can try to disable compression at your origin web server and rely on Cloudflare to [compress content](/speed/optimization/content/compression/) -You can also investigate the configuration of your origin server to make sure the compression is working as expected.