GitHub aggressively caches status badges: need HTTP headers to prevent it.

[nedbat]

My "docs status" badge is stuck on red, because GitHub caches them. Here's the GitHub issue discussing the caching headers needed: github/markup#224 I'm not sure rtfd's redirect to shields.io affects things.

[agjohnson]

Agreed, we should be doing this. If we can't do this in the badge view, we can do it in the production environment.

[mattions]

+1 on this one

[gregmuellegger]

Possible fix: #1653

[flavio]

I'm still affected by this issue even though the code has been merged.

[tbleiker]

Same here...

Edit: When I try to open the link in the browser (e.g. https://readthe.../badge/?version=latest), I get a url redirection (302 Found) and the image from img.shields.io. However, there the Cache-Control header is not set correctly ("public, max-age=86400").

[wishstudio]

+1 to this issue.

[jonasrauber]

This problem still exists. According to GitHub, the solution is to set Expries, Last-Modified or Etag in addition to Cache-Control: no-cache, which is not happening right now.

We're pretty confident that the image caching works. If you're having issues with something like a CI badge, make sure the image has the Cache-Control: no-cache header, and either Expires, Last-Modified or Etag. See the Fastly documentation for more info.

[jonasrauber]

I created a pull-request to fix this: #2927

[ericholscher]

Should be fixed by #3005 👍

[fritzo]

I'm still seeing this issue. To reproduce:

1. create a new rtfd project with broken build
2. add a badge to the project's github README.md
3. fix the rtfd build

[Parker8283]

I am also still seeing this issue with my School Project Repo. The builds were failing, they were fixed about 3 days ago, but the failing badge still persists.