Skip to main content
Redirection from Origin is a CDN resource option that controls how the CDN handles HTTP 3xx redirect responses from the origin.

​
About redirection from origin

The Redirection from Origin option controls whether the CDN follows redirects returned by the origin. By default, this option is disabled, which means that when the origin returns an HTTP 3xx status code, the CDN caches and serves this response to the end user. When the option is enabled, the CDN automatically retrieves the target content from the new location, which is then cached and returned to the end user.
Enabling or disabling this option may cause users to receive an outdated version of the content. Purge the cache after making changes.

​
Configuration

Configure origin redirection via the Customer Portal or REST API.
To configure origin redirection using the Gcore Customer Portal:1. Navigate to CDN and select the CDN resource to configure.
CDN resources list
2. In the sidebar, under the Cache section, select Redirection from origin.
CDN resource settings with Cache section open
3. Toggle Follow redirect from origin on.
Follow redirect from origin toggle enabled with status codes field
4. Select one or more status codes in the Choose redirect status codes field. The options are:
  • 301 — to follow redirect for status code HTTP 301
  • 302 — selected by default; follows redirect for status code HTTP 302
  • 303 — to follow redirect for status code HTTP 303
  • 307 — to follow redirect for status code HTTP 307
  • 308 — to follow redirect for status code HTTP 308
Choose redirect status codes dropdown
5. Click Save changes. Allow at least 15 minutes for the changes to take effect.
After saving, purge the cache so that end users receive updated content.