CDN timeouts

Gcore CDN Edge Network servers use these timeout defaults when proxying to origins and handling client requests. Several values differ from stock Nginx defaults. Decrease proxy_connect_timeout and proxy_read_timeout for individual CDN resources with the timeout settings in the Gcore Customer Portal. Enterprise customers can ask Gcore Support to increase proxy_connect_timeout above 5 s or proxy_read_timeout above 30 s.

Directive	Definition	Value
proxy_read_timeout	Maximum interval between successive read operations while receiving a response from the origin. If the origin sends no data during this interval, the connection closes	30 s
proxy_connect_timeout	Time limit for establishing a connection with a proxied origin	5 s
proxy_send_timeout	Maximum interval between successive write operations while sending a request to the origin. If the origin accepts no data during this interval, the connection closes	30 s
client_header_timeout	Time limit for reading the client request header. If the full header is not received in time, the client receives `408 Request Timeout`	10 s
client_body_timeout	Maximum interval between successive read operations while receiving the client request body. If the client sends no data during this interval, it receives `408 Request Timeout`	30 s
resolver_timeout	Time limit for DNS name resolution	5 s
ssl_session_timeout	How long a client can reuse SSL session parameters	2 h
keepalive_timeout	Idle time after which a keep-alive connection closes. Also applies to HTTP/2 connections and replaces the obsolete Nginx `http2_idle_timeout` directive	15 s

⌘I

Account settings

Developer Tools

CDN

FastEdge

Edge Cloud

AI

Gclaw

Managed DNS

Public DNS

Hosting

Colocation

Object Storage

Video Streaming

DDoS protection

Edge Proxy

WAAP