Thanks for the help.

I reviewed my logs and couldn't find any instances of application errors 
rendering my css file.  I still believe it is a caching problem with 
heroku/varnish.  I also couldn't find any way to tell heroku to clear its 

I was experimenting and if I inline my stylesheet, instead of linking to 
it, I get the latest version rendered just fine.  This is my workaround for 

I would still like to have my stylesheet be a link.  Does anyone know how 
to manipulate the cache headers radiant puts on the css files?  I would 
like to put Cache-Control no-cache on my stylesheets to see how it responds.


On Wednesday, June 27, 2012 6:43:10 AM UTC-7, Benny Degezelle wrote:
> From here, it looks like the css gives an application error on every 
> uncached hit. On the second and subsequent hits, the css seems 
> properly rendered. Have a look at your .log to see what causes the 
> application error, that should give a good clue. 
> On 27 jun, 09:32, jsmorris <> wrote: 
> > Every time I hit the url to a css file coming from my Radiant CMS app, I 
> am 
> > getting a different content of the file.  For example, try the following 
> url 
> > 
> > 
> > 
> > and refresh it 5 or 6 times.  You will notice that the response text is 
> > different each time (at least that is what I am seeing). 
> > 
> > At first I thought it might be a caching problem, but I don't think that 
> is 
> > it.  It seems that Radiant CMS is servering up a different "version" of 
> the 
> > css file each time.  The content of my site seems to be served correctly 
> > each time.  I haven't looked at the js files to see if they show the 
> same 
> > behavior. 
> > 
> > I am running a Radiant 1.0.1 site via the gem, rails 2.3.14 on heroku 
> stack 
> > bamboo-ree-1.8.7. 
> > 
> > I do not see this behavior when I run locally with WEBrick. 
> > 
> > Does anyone have an idea of what might be going on?  Is there something 
> > else I need to be looking at?

Reply via email to