 Search the Knowledgebase |
 Browse by Category |
|
|
|
|
|
| How does Origin Pull work? |
|
Thank you for rating this answer.
|
Origin Pull is a CDN method by which content is pulled from a web server of your choice instead of being uploaded directly to the CDN. In essence, this means that your SoftLayer server is now the source of content being pulled by the CDN and thus controls what is actually on the CDN. This only works for the HTTP method whereas the flash (rtmp) and windows media (mms) protocols still require files to be uploaded manually. When a request is sent to the CDN asking for a document the CDN would look to the configured domain to pull that document. For example, if you had your CDN Origin Pull configured to pull from “mytestdomain.com” and you requested the document http://http.cdnlayer.com/myaccounthere/files/picture_of_car.jpg then the CDN would request http://mytestdomain.com/files/picture_of_car.jpg from your web server. If this file is found the CDN would then pull that file and store it on the CDN for the time specified in your max-age setting.
Origin pull determines if content needs to be pulled from your server via the “Cache-Control” headers. These headers typically specify the max-age, proxy-revalidate and must-revalidate headers, as well as some others.
Please note that use of the ‘private’ option in the Cache-Control header will render the CDN useless as it would not be able to store the document. This is also the case if you use the ‘no-cache’ option.
We recommend using no less than a 5 to 10 minute max-age setting for your content. If no max-age option is specified in the Cache-Control headers, your content may be cached for up to 24 hours before being refreshed.
|
| Related Articles |
|
No related articles were found.
|
| Attachments |
|
No attachments were found.
|
Print this page
Email this page
Post a comment
Subscribe me
Add to favorites
Remove Highlighting
Edit this Article
