Broken on Github Readme
Manishearth opened this issue · comments
Also, @ligthyear, clippy.bashy.io is down?
I don't think the cache control header is the problem – it doesn't make sense as we are just redirecting to shields.io anyways and they do have a cache control header. I think the redirect might actually be the problem. Github caches the badges when rendering the README, which means they are downloaded first – and I am afraid github doesn't follow the redirects..
Not 100% sure which one of them actually fixed it – thought I didn't see any changes until after I changed the 301 Redirect – BUT it works now. Rebuilding right now (thought the exact version is already deployed :) )
Still stuck in the state "linting" for me. https://github.com/skade/html_safe_buffer
@skade could try to refresh the GitHub cached version? Just push a new
revision to that file (just add a ? in the URL or so). Does that fix it?
Weird though, as prior it would cause no rendering to happen at all. I am
afraid that GitHub might ignore the expiration of our redirects and caches
only the last result - and shields.io report static badges with "never
expire". Might have to render our own badges after all..
On 7 Mar 2016 02:28, "Florian Gilcher" notifications@github.com wrote:
Still stuck in the state "linting" for me.
https://github.com/skade/html_safe_buffer—
Reply to this email directly or view it on GitHub
#16 (comment)
.
It works now