403 responses from camo.githubusercontent.com about shields HOT 3 CLOSED

Hello. I'm seeing the same behaviour as you - lots of badges not showing in READMEs on NPM due to a 403 from camo.

This isn't an issue with shields though. The badges are being served fine from shields.io itself.

If you look at some projects that include images from elsewhere in their README on NPM, you'll notice that those images are broken too.

For example compare
https://www.npmjs.com/package/express?activeTab=readme
https://github.com/expressjs/express/blob/master/Readme.md
( https://i.cloudup.com/zfY6lL7eFa-3000x3000.png doesn't display on npm)

https://www.npmjs.com/package/passport?activeTab=readme
https://github.com/jaredhanson/passport/blob/master/README.md
( https://cdn.auth0.com/img/passport-banner-github.png doesn't display on npm)

You'll notice the banner images are broken for the same reason - it is a more general issue with images.

I'd suggest raising this issue with NPM or GitHub support. This camo proxy is not maintained by us.

Thanks

from shields.

Interestingly, the images do seem to be gradually re-appearing on NPM.

My guess is that there is a load of bad data in the cache and as the cached assets expire, the bad data is gradually being replaced with good.

from shields.

Yes, I've checked again today and images are loading again.

from shields.