Icon

Improving user experience by presenting a friendly HTML page during service disruptions and implementing automated retries helps maintain engagement and reduces the perceived downtime for end-users. This approach also reduces the load on the origin server by caching error responses.

Loading...

https://www.edgecompute.live/api/originoverload.php

Copied to clipboard!

Translates a HTTP 503 status code (service unavailable) from an overloaded origin into an HTML page presenting the information in a more user-friendly way. It includes JavaScript to retry after the period indicated by the ‘Retry-After’ header from the origin, if present. Otherwise, it retries after a default number of seconds. Configuring the property to cache HTTP error responses, even for a short duration, makes sense for dynamic content.

Icon landscape
Cache Integration

Combine performance benefits from CDN caching with dynamic edge compute logic.

Icon landscape
Dynamic Flexibilty

Modify in-flight content on its way between client and origin server and back to clients.

Icon landscape
Ease Development

Enable developers to modify application behavior without touching origin server logic.

Icon landscape
Improve Experience

Add additional features on top of your existing infrastructure to improve the user experience.

Related Examples

View More
Icon Card background
API Orchestration

Demonstrates how EdgeWorkers can be used to merge multiple internal APIs into a single API response from a user experience perspective.

View Case
Icon Card background
Cachekey Device Type

This example includes the device type (tablet or mobile) from a PMUSER variable in the computed cache key for an Edge Server.

View Case
Icon Card background
Device Routing

Implements modification of the forward origin path of the URL to return device-specific content.

View Case