This documentation and answers will help you get started and master the way you use PageCDN for better content delivery.


Common errors and problems and how to solve them.

Supported Origin Headers

PageCDN whitelists headers before sending files to the browser. Here is a list of Origin specified headers that PageCDN forwards to the browser:

  • Last-Modified
  • Content-Type
  • Content-Disposition - only if the repo is NOT configured to 'Force Downloads'. If a repo is configured to 'Force Downloads' through the repo configuration panel, the Content-Disposition header sent by the origin server, if any, is ignored and CDN specifies own Content-Disposition header.
  • Cache-Control - only if repo is configured to honor origin's cache control headers.
  • Expires - only if repo is configured to honor origin's cache control headers.

To change how browsers cache the files delivered by PageCDN:

  • Goto 'My Websites' page and choose the CDN repo that you want to configure.
  • On the next (CDN Files) page, click 'Configure' to open configuration form.
  • Scroll down the configuration form a little and look for 'Browser Cache TTL' option.
  • There you can specify Expiry time (or Time to Live) of browser cache in Seconds, Minutes, upto Years.
  • To cache files forever in the browser, input -1 in the box.
  • To allow the origin server to specify cache control headers for each file, input 0 in the box.
  • Hit 'Save Changes'.

PageCDN allows you to specify TTL at repo level only. For a more fine grained control over caching of individual files, it is recommended to specify 0 to disable CDN override and specify cache-control header at origin server.