Please contact your support team if you have a question or need assistance for any Rackspace products, services, or articles.
This question is not answered.
Would someone please be so kind to answer/clarify my questions in regards to following thread.https://community.rackspace.com/products/f/25/p/5069/12101
What is minimum TTL that can be set on container?
Essentially what I need is for the file to be overwritten and new file available immediately. If the overwrite works fine on the second PUT why doesn't work on the third PUT?
What/how can I make sure each time PUT is performed existing file is overwritten with new file?
Does PUT overwriting the existing file count as a purge?
Hey there -
I moved this back into our Developer/API section to get their eyes on it to answer some of your more nuanced questions.
One question I can answer for you now is the minimum TTL. The default time to live (TTL) value is 72 hours (259200 seconds), with a minimum of 15 minutes (900 seconds) and a maximum of 1 year (31536000 seconds).
Alan BushTechnical Community ManagerRackspace Cloud
From one of our wonderful support guys: You can just upload the new file with the same name. It will replace the original. Then you need to issue the purge to ensure that any subsequent pulls from cdn edge nodes grab the new file. If you purge before uploading, the file can be cached on the edge node for the length of the TTL, and you will need to purge the file again in order for the new one to show.
Also note: Deleting/changing an object does not cause an object to be purged from the CDN. Usually it is ok to just let the object drop out of cache on its own. If you need objects to be removed from the CDN after they are removed/changed, then you would need to either issue a purge request on the object themselves (max 25 per day), or contact support to have their container purged for them.
If you reach the purge limit, you will receive the 498 response code.
Hope this helps!
Regards,Catherine (Rackspace Information Developer)
The Rackspace Community (“Community”) is provided “AS IS” without warranty of any kind. The information on the Community sites is created by members of the Community and is intended for reference and general discussions only. Although some of the content may contain information provided by Rackspace employees, it does not represent an assessment of a particular customer environment or an assessment of any specific compliance with laws or regulations or constitute advice. We recommend that you engage additional expertise in order to further evaluate applicable requirements for your specific environment. For customer specific support issues please contact your Rackspace Support Team.READ MORE
RACKSPACE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THE RACKSPACE OPEN CLOUD COMMUNITY SITE. RACKSPACE RESERVES THE RIGHT TO DISCONTINUE OR MAKE CHANGES TO ITS SERVICES OFFERINGS AND SPECIFICATIONS AT ANY TIME WITHOUT NOTICE. USERS MUST TAKE FULL RESPONSIBILITY FOR APPLICATION OF ANY SERVICES AND/OR PROCESSES MENTIONED IN ANY COMMUNITY DISCUSSIONS. EXCEPT AS SET FORTH IN RACKSPACE GENERAL TERMS AND CONDITIONS, CLOUD TERMS OF SERVICE AND/OR OTHER AGREEMENT YOU SIGN WITH RACKSPACE, RACKSPACE ASSUMES NO LIABILITY WHATSOEVER, AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO ITS SERVICES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
ALTHOUGH PART OF THE COMMUNITY GENERATED CONTENT MAY EXPLAIN HOW RACKSPACE SERVICES MAY WORK WITH THIRD PARTY PRODUCTS, THE INFORMATION CONTAINED IN THE COMMUNITY DISCUSSIONS IS NOT DESIGNED TO WORK WITH ALL SCENARIOS. ANY USE OR CHANGES TO THIRD PARTY PRODUCTS AND/OR CONFIGURATIONS SHOULD BE MADE AT THE DISCRETION OF YOUR ADMINISTRATORS AND SUBJECT TO THE APPLICABLE TERMS AND CONDITIONS OF SUCH THIRD PARTY. EVEN THOUGH RACKSPACE EMPLOYEES MAY PARTICIPATE IN THE COMMUNITY DISCUSSIONS, RACKSPACE DOES NOT PROVIDE TECHNICAL SUPPORT FOR THIRD PARTY PRODUCTS, OTHER THAN SPECIFIED IN YOUR HOSTING SERVICES AGREEMENT YOU HAVE SIGNED WITH RACKSPACE AND RACKSPACE ACCEPTS NO RESPONSIBILITY FOR THIRD-PARTY PRODUCTS.READ LESS