Skip to main content
Git Interface

Debug Headers

Learn how to use the debug headers to help identify and fix issues that you may run into while using CloudFlow.

Enable debug headers​

CloudFlow provides a range of debug headers that are disabled by default. These headers can be enabled by sending the section-debug request header with any value. When this request header is received, CloudFlow will respond with the following debug headers:

  • section-origin-status
  • section-origin-failure
  • section-origin-dns-failure
  • section-origin-time-seconds

section-origin-status​

When no bytes are received from the origin web server s​ection-origin-status header is set to 000 (e.g. DNS failures).

When a response is received from the origin web server section-origin-status is set to the upstream status if it is a single status code or the last value when the upstream status is an array of response codes (e.g. due to retries).

section-origin-failure​

When no bytes/response is received from the origin web server and CloudFlow can resolve the DNS for the origin web server (a request to the origin is made) section-origin-failure header is set to true, otherwise it is not set.

section-origin-dns-failure​

When CloudFlow is unable to resolve the DNS of the origin web server section-origin-dns-failure header is set to true, otherwise it is set to false.

section-origin-time-seconds​

This header indicates in seconds the time taken by the CloudFlow platform to receive the entire response from the origin web server.