Repository navigation
[JENKINS-17684] Dashboard web pages don't render correctly in Chrome because of bad cache/session #14507
Description
After using Chrome for a day, the page renders incorrectly.
Screenshot: http://imgur.com/9Y11bqz
It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine.
If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s.
If I clear the cache manually using the Chrome Web settings, then everything works fine again.
I went to #jenkins on freenode and apparently other people were having the same issue.
*Update* I can make the error go away by simply clearing the jenkins cookie and leaving the rest of the cache intact. It seems the error is session related (all the cookie contains is a session id).
I am using the GitHub plugin for authentication/authorization.
Originally reported by 
rburhum, imported from: Dashboard web pages don't render correctly in Chrome because of bad cache/session
- assignee:
accountapp
- status: Reopened
- priority: Major
- component(s): core
- label(s): 1.509.2-fixed
- resolution: Unresolved
- votes: 24
- watchers: 45
- imported: 2025-11-24
Raw content of original issue
After using Chrome for a day, the page renders incorrectly.
Screenshot: http://imgur.com/9Y11bqz
It doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine.
If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s.
If I clear the cache manually using the Chrome Web settings, then everything works fine again.
I went to #jenkins on freenode and apparently other people were having the same issue.
*Update* I can make the error go away by simply clearing the jenkins cookie and leaving the rest of the cache intact. It seems the error is session related (all the cookie contains is a session id).
I am using the GitHub plugin for authentication/authorization.
environment
Google Chrome 26.0.1410.65 (Official Build 193261) <br/>
OS Mac OS X <br/>
WebKit 537.31 (@147513)<br/>
JavaScript V8 3.16.14.11<br/>
Flash 11.7.700.169<br/>
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.65 Safari/537.31<br/>
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome -psn_0_17293437 --flag-switches-begin --enable-expose-for-tabs --enable-experimental-extension-apis --sync-keystore-encryption --flag-switches-end<br/>
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome<br/>
Profile Path /Users/rburhum/Library/Application Support/Google/Chrome/Default<br/>
Variations 853359fa-33ba05a4<br/>
5f9f065f-15eb91be<br/>
b03ddc1f-2d9ef0cc<br/>
f9b252d0-fd526c81<br/>
ca6785ad-766fa2d<br/>
3709139-766fa2d<br/>
ff3fc1a6-766fa2d<br/>
d86b76a4-d674141c<br/>
7f6da4bf-cda32b90<br/>
75f7fb7e-611a9f49<br/>
24dca50e-837c4893<br/>
ca65a9fe-91ac3782<br/>
82d91892-3d47f4f4<br/>
3028188e-d60b5a5f<br/>
5a3c10b5-e1cc0f14<br/>
244ca1ac-4ad60575<br/>
246fb659-75cb33fc<br/>
f296190c-19dcaa1a<br/>
4442aae2-d7f6b13c<br/>
75f0f0a0-e1cc0f14<br/>
e2b18481-6bdfffe7<br/>
e7e71889-e1cc0f14
Activity
jenkins-infra-bot commentedon Apr 19, 2013
Raw content of original comment:
If anyone else sees a similar issue, please attach your screenshots as well.
http://imgur.com/9Y11bqz has no table borders, which indicates that style.css isn't kicking in. The chrome dev output indicates that Jenkins had sent 304 without content, which then makes me wonder what Chrome thinks it has in its cache.
One would think somehow the cache gets poluted, and Chrome isn't even noticing that because the server keeps sending 304 to the client.
jenkins-infra-bot commentedon Apr 22, 2013
Raw content of original comment:
Same problem here with Google Chrome, Version 26.0.1410.64 m under Windows 7, 64-bit.
Can't enforce the bug, but it happens quite regularly after automatic refresh ran in the background for a while. Agree that it looks like a problem with CSS. Maybe a bug of Chrome, not necessarily Jenkins.
jenkins-infra-bot commentedon Apr 22, 2013
Raw content of original comment:
I can get it to happen without having automatic refresh for awhile. After the site goes into a bad state, it remain so.
I was also told (in IRC) to look at the contents of screen.css. I don't see any screen.css file though.
*I found something interesting though*. If I delete the jenkins cookie and open the page again, the page starts working again. The cookie contains the session value, so it seems that the error is related to a session id expiring. I am using the GitHub plugin for authentication/authorization.
jenkins-infra-bot commentedon Apr 22, 2013
Raw content of original comment:
I am going to update the main bug description to account for this.
jenkins-infra-bot commentedon Apr 22, 2013
Raw content of original comment:
Seeing something similar quite frequently (Jenkins ver. 1.480.2, Chrome Version 26.0.1410.64)
I can resolve it by forcing a full reload (CTRL+SHIFT+R)
jenkins-infra-bot commentedon Apr 23, 2013
mika:
Raw content of original comment:
Seeing the same problem here on Jenkins v1.512 + Chrome 26.0.1410.43-r189671, ctrl-shift-r works around the issue.
Might be related to
JENKINS-17526?jenkins-infra-bot commentedon Apr 23, 2013
Raw content of original comment:
It does look like it is similar to
JENKINS-17526To clarify:
It does look like it is similar to
JENKINS-17526jenkins-infra-bot commentedon Apr 24, 2013
Raw content of original comment:
Same issue for me, jenkins 1.512 Chrome 26.0.1410.64 m, Win 7 64bit. Usually I use ctrl + F5 which clears cache for web page and helps. Offtop: Chrome have now new feature for cleaning cache you can check http://stackoverflow.com/questions/12633425/chrome-browser-reload-options-new-feature
jenkins-infra-bot commentedon May 14, 2013
Raw content of original comment:
I'm having the same problem with jira v5.2.8#851-sha1:3262fdc with Chrome 26.0.1410.65 on Max OSX 10.7.5. If I hold Option while clicking refresh, it gets fixed for a short time.
jenkins-infra-bot commentedon May 15, 2013
Raw content of original comment:
15:51:06 <+rpetti> IMO, just assign it to kohsuke
jenkins-infra-bot commentedon May 17, 2013
mbarczak:
Raw content of original comment:
Same problem here : Chrome 26 , Jenkins 1.489 . Ctrl+Shift+R fixes problem for a while
jenkins-infra-bot commentedon May 20, 2013
vladichko:
Raw content of original comment:
this is how it looks for me at chrome Version 26.0.1410.64 m(attached jenkins-gui.png)
jenkins-infra-bot commentedon May 21, 2013
Raw content of original comment:
Seeing the same issue with Jenkins 1.509.1 running as a native package on CentOS release 6.4. Ctrl-shift-R seems to fix the issue. Attaching jenkins_css_3.PNG. Chrome Version 26.0.1410.64 m.
jenkins-infra-bot commentedon May 21, 2013
Raw content of original comment:
So, I fix a source code to exclude content-type when 304, and trying it in my using Jenkins server.
If no problem for a week, I'll send a pull request this. Currently, content-type header is normal and no problem occurs for three days.
It's ok that you fix in main repository source code before sending my pull request. At which time, consider about other headers (Content-length, content-disposition, and so on), please.
I think that a problem may be sending content-type header when http response is 304 in winstone.
Looking a capture http://imgur.com/9Y11bqz, css files are interpreted as 'text/html', but should be 'text/css'.
According to RFC, the 304 response should not include non-releated header.
For example, Plack ( which is web app framework by Perl ) excludes Content-Type / Content-Length / Content-Disposition headers.
So, I fix a source code to exclude content-type when 304, and trying it in my using Jenkins server.
If no problem for a week, I'll send a pull request this.
Currently, content-type header is normal and no problem occurs for three days.
It's ok that you fix in main repository source code before sending my pull request.
At which time, consider about other headers (Content-length, content-disposition, and so on), please.
jenkins-infra-bot commentedon May 21, 2013
Raw content of original comment:
Nice! That sounds like a plausible explanation, and other people are having similar problems with Chrome:
http://productforums.google.com/forum/#!msg/chrome/zID6uQQfKH8/AOUiKiAp8fwJ
https://code.google.com/p/chromium/issues/detail?id=176430
I guess everybody here seeing this issue is running Winstone?
12 remaining items
jenkins-infra-bot commentedon Jun 10, 2013
Raw content of original comment:
Watch the changelog.
jenkins-infra-bot commentedon Jun 10, 2013
Raw content of original comment:
Thanks very much to both of you and sorry for my newbie-ness
This issue and
JENKINS-10442are the first two real issues I've experienced on Jenkins. Looking forward to the fixes being rolled out.jenkins-infra-bot commentedon Jun 11, 2013
Raw content of original comment:
Version 1.518 was released today, which fixes this issue.
jenkins-infra-bot commentedon Jun 11, 2013
Raw content of original comment:
Verified. It's beautiful! Great work! Thanks.
jenkins-infra-bot commentedon Jun 20, 2013
Raw content of original comment:
Code changed in jenkins
User: Jesse Glick
Path:
war/pom.xml
http://jenkins-ci.org/commit/jenkins/804c2ed42e15dcf8576f1697d174550e1370b779
Log:
[FIXED JENKINS-17684] Integrate new Winstone with caching fix.
Cherry-picked-from: 0866cf5
jenkins-infra-bot commentedon Jun 23, 2013
lacostej:
Raw content of original comment:
Would like to have this backported to lts-candidate. Seems I cannot add a label on closed issues.
jenkins-infra-bot commentedon Jul 19, 2016
srinivav:
Raw content of original comment:
I just upgraded to 2.7.1 I am seeing this problem again. I am not able to reach the post build sections of the dashboard at all.
Please see
jenkins-infra-bot commentedon Nov 24, 2025
[Original
is_duplicated_byfrom Jira: JENKINS-17526]