> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/cdn/cdn-resource-options/general/customize-connection-and-read-timeouts) in the [Gcore Customer Portal](https://portal.gcore.com). Enterprise customers can ask [Gcore Support](mailto:support@gcore.com) to increase `proxy_connect_timeout` above 5 s or `proxy_read_timeout` above 30 s.

| Directive                                                                                                  | Definition                                                                                                                                                                       | Value |
| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
| [proxy\_read\_timeout](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#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](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_connect_timeout) | Time limit for establishing a connection with a proxied origin                                                                                                                   | 5 s   |
| [proxy\_send\_timeout](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#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](https://nginx.org/en/docs/http/ngx_http_core_module.html#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](https://nginx.org/en/docs/http/ngx_http_core_module.html#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](https://nginx.org/en/docs/http/ngx_http_core_module.html#resolver_timeout)             | Time limit for DNS name resolution                                                                                                                                               | 5 s   |
| [ssl\_session\_timeout](https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_session_timeout)       | How long a client can reuse SSL session parameters                                                                                                                               | 2 h   |
| [keepalive\_timeout](https://nginx.org/en/docs/http/ngx_http_core_module.html#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  |