Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I'm getting a very strange error on http://cure.org where the following PNG image is not being delivered from the CDN to webkit browsers (both Chrome and Safari), but Firefox is loading it just fine.

Even more strange is that only one image appears to be affected. Other PNGs, include the site main sprite, are loading just fine.

The affected image url is: http://c615642.r42.cf2.rackcdn.com/img/list-focus-bg.png which when it from Chrome and Safari return a "Webpage not available" result.

Does this made any sense? Why would Firefox be loading the image but not Safari or Chrome.

Also, my testing so far has only included Mac boxes. However, my colleague on Linux is loading the image fine from both FF on Kubuntu and Chrome on Kubuntu.

Edit: After clearing my cache in FF it's not appearing there either.

Turns out that according to HttpFox, rackspace is giving me an old version of the file.

We're going to contact Rackspace about it, but my tech dir says sometimes routers or ISP's can cache the file along the way.

enter image description here

share|improve this question
    
I can see it with Safari (5.0.5) on OSX (10.6.8). –  Chopper3 Jul 8 '11 at 15:43
    
The image is also visible (both on page and directly) with Chrome (14.0.803.0) on Windows 7 (64-bit) –  cyberx86 Jul 8 '11 at 15:50
    
Turns out that HttpFox shows via the headers that I'm getting an old version of the file. –  Joel Glovier Jul 8 '11 at 16:31
add comment

migrated from serverfault.com Jul 8 '11 at 17:36

This question came from our site for professional system and network administrators.

1 Answer

up vote 4 down vote accepted

Here's what Fiddler reports for that image:

HTTP/1.1 Cache-Control Header is present: public, max-age=2529648
    public: This response MAY be cached by any cache.
    max-age: This resource will expire in 29.28 days. [2529648 sec]

So, you TOLD Rackspace to cache the image for 30 days on their CDN. That's what they're doing, which is why you are seeing older versions of the file from some of the CDN nodes that had the old version in their caches. The default is 24 hours, so you must have over-ridden it via their website or their API. Did you copy-and-paste code or something?

To override the 30 days of caching you set up, you need to change the URL of the image in the source page, or tell Rackspace to purge the old version from their CDN nodes: http://www.rackspace.com/cloud/blog/2011/02/25/cloud-files-cdn-gets-edge-purge/

share|improve this answer
    
THANK YOU for your response. I'll pass it along. –  Joel Glovier Jul 10 '11 at 22:59
    
please accept my answer here if you found it useful –  rmalayter Jul 11 '11 at 20:15
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.