 Search the Knowledgebase |
 Browse by Category |
|
|
|
|
|
| How does Origin Pull work? |
|
Thank you for rating this answer.
|
OW DOES ORIGIN PULL WORK?
Origin Pull is the method of transferring data to the CDN automatically from a webserver as opposed to manually uploading the content. This method of uploading data to the CDN can be used for HTTP, on demand Flash and on demand Windows Media content. Once the initial configuration is completed, the content will become available to the CDN by simply requesting the CDN URL associated with that content.
For example:
You can have the Edge CDN URL point to a server to obtain content. The Edge CDN URL will be http://SLXXX.cdn.softlayer.net, and your Origin URL will be http://myserver.com.
You would have something like this in your HTML on your website:
<IMG SRC=”http://SLXXX.cdn.softlayer.net/images/picture.jpg”>
The IMG tag will tell the client to retrieve the picture.jpg image from the Edge CDN rather than directly to your server. If the image is not already stored on the CDN cache, then it will go to your Origin URL, retrieve the content from the images directory, and then display it while caching the image on the CDN server. On the next request, the image will be served directly from the CDN rather than your server and subsequent page loadings will be much faster.
With Origin Pull, the CDN determines if content will need to be pulled from your server via the “Cache-Control” headers configured on your webserver. The CDN will honor most standard Cache-Control options such as max-age, proxy-revalidate, must-revalidate.
Please note that the use of the ”private” and “no-cache” option in the Cache-Control headers will result in the CDN pulling a new version of the content for each request it receives as the headers will instruct it not to cache that content.
We recommend not setting your max-age to less than 5 to 10 minutes as this will put excessive load on your webserver and result in less optimal performance. Be aware that if content on the webserver has been updated, each POP will continue to serve the old cached version until that cache is purged or the cache on the POP expires. If no max-age header is set, the default max-age of 24 hours will be used.
|
| 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