Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Edge CDN Status Codes and Behaviour

Request Mode Headers

We have implemented some new headers with the Edge CDN offering to improve your integration capabilities.

Every response will contain the X-Prerender-Request-ID header which is a unique identifier to help to find each request's history.

X-Prerender-Mode indicates a CacheHit or CacheMiss mode. With this the integration and integrator can better understand which content is being served in case the system is seeing a new URL and activated the pass through mode for the request.

PassThrough headers
Cache-Control, Pragma, Expires the following headers are applied to indicate to the crawler to not to cache the current response as this comes from a pass through mode, and the expiration is set 60 second in the future. This will allow us to render the content and wait for the crawler to check back for the rendered content.

CacheHit headers
Expires, Last-Modified headers are attached to the content and configured respectfully to the cache's state. With this we can indicate that the content was last rendered at X, and there will be new content at Y date. The expiration is calculated based on the recache interval.

HTTP 401 Response

Indicates that the request is not properly authenticated or the account does not have access for the Edge CDN network.

To authenticate the request your integration has to send the following HTTP header

X-Prerender-Token: %YOUR_RENDER_TOKEN%

Each response comes with additional hints:

  • Missing [X-Prerender-Token] header when the header is not present in the request
  • Invalid environment token when the token's format is not matching the /^[a-zA-Z0-9]{20}$/ pattern
  • Environment token is not registered. Please visit your dashboard and turn on the Edge option for your account. when your account does not have access for the Edge CDN service.

HTTP 500 Response

Uncommon response in case your environment configuration contains some irregurality. Please open a ticket with our support team, as this case requires us to verify your configuration.

Addition hints:

  • Invalid configuration is detected, please notify our support team
  • Could not fetch from the origin, please notify our support team can happen when your servers are blocking our request or the requested domain does not exists.

HTTP 502 Response

Caused by inproper requests, usually reflects an integration which forwards requests to our service even when it should not.

Additional hints:

  • Prerender loop detected, please verify your integration when the user agent string contains the Prerender word, happens when the integration is forwarding our own rendering process to our proxy. Please verify your forwarind rules.
  • %path% is not renderable hints that our system received a static resource call which should not be served by Prerender but the origin server. Can be corrected by filtering forwarind request for non static resources only.

HTTP 400 Response (Our Fault)

Outstanding case when our integration detected an issue in the process and abadoned it. We log those errors and when a HTTP 400 is responded it means that we need to improve on our error messages.
Please note, this error can contain hints about the problem to help debugging but not an error which need to be handled by your team / integration.