| We moved this page to our Documentation Portal. You can find the latest updates here. |
What is HTTP Pull CDN?
HTTP Pull is probably the most frequently used CDN method/protocol. It's recommended for the delivery of small static content via CDN edge servers - content like images, css and pdf files. With HTTP Pull, content is cached on edge servers when a user requests that content.
The detailed workflow is as follows:
(1) A visitor requests content from a website.
(2) The OnApp core CDN logic determines which cdn edge server (owned or subscribed) is best placed to deliver that content.
(3) If the content is not already cached on that edge server, the CDN pulls the content from the origin via HTTP port 80.
Site owners may set the cache expiry on the origin, or define it in the advanced settings of the relevant CDN Resource.
To offer HTTP Pull service to your clients, you would need HTTP edge servers. You can build it on your own, or subscribe for HTTP cdn locations in OnApp federation (via dashboard).