Badges on the README not loading properly

[olivierlacan]

Not sure what's causing that, bad GitHub cache?

[nathany]

I think so (the images do load if I copy the url to them). Will check back tomorrow.

[nathany]

Still not working.

https://twitter.com/nathany/status/420955697707114496
If no response, I'll write GitHub support.

[jessesquires]

Hey guys. I'm also experiencing this (example).

However, as @nathany noted, the images do load from the URL directly: http://b.repl.ca/v1/license-GPL-blue.png

[nathany]

@jessesquires I had no idea this was impacting others, thanks for the heads up!

I just wrote an email to GitHub support.

[nathany]

I still have no idea how to fix this. Feel like my hands are tied. :-(

https://twitter.com/nathany/status/421169838770229248

[nathany]

I haven't received any reply from GitHub support yet, not even an automated response. They may just be backlogged with tickets around yesterdays outage. I sent a new request through their contact form, trying to word it to better convey that this is an issue that is on GitHub/Fastly's side and not an issue that I should've just reported to Buckler.

Fastly caching issue with the badges we generate

Good morning,

I am a contributor to the Buckler project which people use for badges across GitHub such as license | MIT which is static. We serve these without SSL which means they are cached by Fastly.

As of the evening of Tue Jan 7 all these badges, including newly generating ones are failing to resolve on GitHub. The url embedded in the README does generate the badge, but the Fastly cache of these badges causes an error.

Please provide a resolution. Here is the relevant issue:
https://github.com/badges/buckler/issues/27

Nathan.

[aspires]

@nathany It looks like the cache is getting a 404 from the backend. This is what I get after running a purge on the image

☁  ~  curl -I https://github-camo.global.ssl.fastly.net/ea1832a146b4d36c596ccd11a5c4ca88a3663c36/687474703a2f2f622e7265706c2e63612f76312f7573652d6275636b6c65722d626c75652e706e67
HTTP/1.1 404 Not Found
Date: Thu, 09 Jan 2014 17:53:35 GMT
Server: Apache
Content-Length: 9
Accept-Ranges: bytes
Via: 1.1 varnish
Age: 25
X-Served-By: cache-sv63-SJC3
X-Cache: HIT
X-Cache-Hits: 3
X-Timer: S1389290015.543076277,VS0,VE0

I did this for ~5 images just to be sure.

[nathany]

@aspires Odd, see below. Thanks for looking into it.

$ curl -I http://b.repl.ca/v1/license-GPL-blue.png
HTTP/1.1 200 OK
Date: Thu, 09 Jan 2014 18:04:03 GMT
Cache-Control: public
Content-Type: image/png
Expires: Wed, 07 Jan 2015 01:04:03 GMT
Last-Modified: Tue, 03 Dec 2013 06:20:19 GMT

[jessesquires]

@nathany -- thanks for helping with this.

what exactly is the status of using https to prevent this issue?

[nathany]

@jessesquires That would be up to @jbowes to purchase and setup an SSL cert for b.repl.ca.

It's quite sad that I still haven't heard a peep from GitHub on resolving the present issue. I've had an email exchange with @aspires from Fastly, and it doesn't appear anything can be done from their side.

[nathany]

@vmg Thanks for prodding some GitHubbers to look into this badges/shields#103 (comment). @aspires of Fastly has already poked at camo a bit:

So, HEAD requests are working, but not GET requests to GitHub's backend. Unfortunately, there's not much we can do here. I've bumped GitHub's ops team about this though. - Austin

[nathany]

@alindeman got back to me today:

We've fixed an issue on our end related to our image proxy. Would you check to see if your badges are working correctly now?

All looks good.

[jessesquires]

woohoo!! thanks so much @nathany for pursuing this!