CDN timeouts - Gcore Docs

The timeouts set for the servers proxied by the Gcore Edge Network vary from the default values of nginx. The following timeouts are currently in use:

Directive	Definition	Value
proxy_read_timeout	The time limit for receiving a partial response from a proxied server. If no response is received within this time, the connection will be closed. For instructions on how to set up the timeout, check out our dedicated guide.	30s
proxy_connect_timeout	The time limit for establishing a connection with a proxied server. For instructions on how to set up the timeout, check out our dedicated guide.	5s
proxy_send_timeout	The time limit for sending a request to a proxied server. If no response is received within this time, the connection will be closed.	30s
client_header_timeout	The time limit for a proxy server to read a client request header. If the entire header is not received within this time, the client will receive a 408 (request timeout) error.	10s
client_body_timeout	The time limit for a proxy server to read a client request body. If no data is sent within this time, the client will receive a 408 (Request Time-out) error.	30s
resolver_timeout	The time limit for resolving a name.	5s
ssl_session_timeout	The duration for which the client can reuse session parameters.	2h
http2_idle_timeout	The inactivity period after which the connection will be closed.	15s

The timeouts can be changed via Gcore Support if you have an enterprise plan.

HTTP/2 CDN resources overview

⌘I