API
The Gcore Customer Portal is being updated. Screenshots may not show the current version.
CDN
CDN
For static filesFor the entire site
AWS S3B2evolutionClouldFlareConcrete5CraftCs-cartDjango CMSDrupalGoogle Cloud StorageIPBIPSJoomlaKirbyMagentoPerchPrestaShopPyroCMSSocialEngineTypo3vBulletinWebasyst
Gcore pluginRocket pluginW3 Total Cache pluginWP SuperCache plugin
X-CartXenForo
Integrate CDN with FastEdge
Add CDN servers to ACLHTTP/2
Timeouts
BillingCDN resources overview
Specify an originPrivate originEnable SSL ValidationCreate a custom domain (CNAME)SSL certificatesEnable shielding (paid)Suspend a CDN resourceConnection and read timeouts
Configure CDN cachingSet a redirect from an originConfigure browser cachingIgnore Set Cookie or Query stringUse stale cache if origin is unavailableCache ShardingModify cache key
Manage access policiesRedirect from HTTP to HTTPS
OverviewConfigure and use
Specify HTTP methodsSet SNI hostname
Gcore WAAP (Beta)
GZip, BrotliFetch
Status codeLarge files deliveryRewriteWebSockets
Add request headersActivate CORSConfigure response headersManage the Host headerIdentify a user's request protocol
Network limits
Image stack overviewEnable Image stack
Convert to WebP or AVIFChange qualityCropResize
Troubleshooting
Streaming via CDN (for paid tariffs)Geobalancer (for paid tariffs)
Create a ruleCreate a template for rulesAvoid indexing
Origin group
SSL overviewOwn SSL certificateLet's Encrypt certificate
PurgePrefetch
Raw logsLogs uploader (near real-time)Log Viewer (free)
Reports
Grafana reports
Install and integrate with CDNCreate and manage CDN resourcesCopy CDN resourcesCreate a CDN ruleAdd an SSL certificateSet up version control and perform rollback
Error status codesTraceparentContent unavailabilityLow cache hit ratioLow content delivery speedAttaching or issuing an SSL certificate3xx codes4xx codes5xx codes
API
Chosen image
Home/CDN/Getting Started/Timeouts

CDN timeouts

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 technical support if you have an enterprise plan.

Was this article helpful?

Not a Gcore user yet?

Learn more about our next-gen CDN

Go to the product page
Edit on GitHub