Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Build status image's being cached in Chrome #822
I kept seeing Build status failing in my project in a separate branch and created this issue to track:
I then Tweeted @travis-ci and realized it was a cache issue. Upon clearing my cache, the build status correctly showed up as Success.
I'm unsure if this is headers related or yet-another-aggressive-google-cache. Would be great to hear if others are having the same issue.
Let me know if you need more information.
Since I'm observing the same issue, here is some debugging info.
I have two Chrome windows open, one is my "regular" Chrome in which I didn't clear the cache, and the other one is my "incognito" window with a clear cache. I have recently broken the travis build for a project, and it's travis image is here: https://api.travis-ci.org/izuzak/noam.png (shows failing). While my window with a cleared cache shows the correct image (failing), the window which has previously cached the image (success) still shows success. (When I say "browser with a cleared cache", I just mean that I cleared the cache after the latest travis build -- this browser didn't see the previous build status image from travis).
Here are the HTTP requests and responses for both windows:
Request from browser with a non-empty cache (shows wrong image):
Response from browser with a non-empty cache (shows wrong image):
Request from browser with an empty cache (shows correct image):
Response from browser with an empty cache (shows correct image):
Notice that the response in both cases is a
I experienced this same issue, and I'm using Chrome. It's annoying because even if you open the image URL in a separate tab and refresh, it still shows the wrong (failing) status. Altering the URL (e.g. by appending a
@rkh, can you please have a look into this :)
On 13/01/2013, at 9:54 AM, Chris Jerdonek firstname.lastname@example.org wrote: