All Products
Search
Document Center

Edge Security Acceleration:Timeout for HTTP requests to origin

Last Updated:Dec 23, 2025

Setting an appropriate timeout period for HTTP requests to the origin server enhances response efficiency. If the timeout period is too short, network fluctuations can lead to frequent fetch failures from the origin. If it is too long, it may tie up too many connections when the origin is overloaded or unresponsive, disrupting the handling of regular requests.

What is HTTP request time to origin

The HTTP request time to origin measures the duration of Layer 7 HTTP requests when ESA point of presence (POP) forwards these requests to the origin server. This metric does not include the time taken for establishing a Layer 4 TCP connection back to the origin.

image

Before you begin

ESA supports setting a maximum timeout of 300 seconds for the entire connection, including paths within the ESA POP and between the ESA POP and the origin.

The default timeout setting is 30 seconds. We recommend a timeout period no longer than 60 seconds.

Setup

  1. In the ESA console, choose Websites. In the Website column, click the target website.

  2. In the left navigation pane, choose Rules > Origin Rules.

  3. Click Create Rule and enter a Rule Name.

  4. In the If requests match... section, set the request features to match. For more information about how to configure rules, see Rule expression components.

  5. In the Timeout for HTTP Requests to Origin section, click Configure. Enter the timeout period.

    image

References

Rule-related features vary in execution priorityrule behavior, and configuration scope. For more information, see How ESA rules take effect.