479383 - Spread Firefox staging server holding on to its CSS cache / not picking up /reflecting CSS changes

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

Bug 479302 and bug 478362 should be visible on https://spreadfirefox.authstage.mozilla.com/, but for some reason, aren't:

buchanae: yeah, the css has been cached, and I can't get it cleared
buchanae: everything else makes it through
stephend: ah
stephend: oh
stephend: drupal cache, right?
buchanae: i've cleared the drupal cache

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

Seems to be working now; Alex, any idea what fixed this?

Comment 2

[Alex Buchanan [:abuchanan]]

I have no idea.  I tried clearing every cache I could reach, and I tried bypassing the NS by appending ?aslkfd to the URL.  It cleared itself somewhere around 12-1am.

Comment 3

[Alex Buchanan [:abuchanan]]

Also, this has been happening every time I commit CSS changes (and we're doing a lot of those) so any ideas would be much appreciated.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

IT: do you have cycles to look at this?  We're currently experiencing issues with it, so might be a good time to look at it; thanks!

Comment 5

[Jeremy Orem [:oremj]]

Bypassing the NS by appending a random query string didn't work?

Comment 6

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #5)
> Bypassing the NS by appending a random query string didn't work?

AFAIK, it still happens (again, only with CSS changes); pretty sure both Alex and I have tried the cache-override trick, but we'll be sure to test it again and report back when some CSS changes land soonish.

Comment 7

[Alex Buchanan [:abuchanan]]

oremj, any ideas for this?  bypassing the NS with a random query string hasn't worked, neither had clearing the Drupal caches.

Comment 8

[Wil Clouser [:clouserw]]

(In reply to comment #6)
> (In reply to comment #5)
> > Bypassing the NS by appending a random query string didn't work?
> 
> AFAIK, it still happens (again, only with CSS changes); pretty sure both Alex
> and I have tried the cache-override trick, but we'll be sure to test it again
> and report back when some CSS changes land soonish.

Don't forget you'll need to use the random-string on each individual CSS/JS/etc. file, not just the one page.

Comment 9

[Alex Buchanan [:abuchanan]]

> Don't forget you'll need to use the random-string on each individual
> CSS/JS/etc. file, not just the one page.

ah, that did it.

Comment 10

[Alex Buchanan [:abuchanan]]

actually, can we prevent CSS from being cached on the NS for stage only?  That way we can see/QA changes immediately.  It seems to take quite a while to clear itself.

Comment 11

[Jeremy Orem [:oremj]]

I've added nocache headers to *.css via apache.

Comment 12

[Stephen Donner [:stephend] Not actively reading bugmail]

Seems to be fixed for me; lots of CSS fixes landed today (thanks, Neil!), and there wasn't any downtime in picking up those fixes.

Verified.