Iteresting ... so your browser has the css file in its cache and asks Magnolia to send it only if it was modified since the date when the file was put in cache: > If-Modified-Since: Wed, 16 Jul 2008 18:59:54 GMT
Since the file was not modified, Magnolia correctly responds with: > HTTP/1.x 304 Not Modified Therefore browser should render cached version of the file. When you said you cleared cache 10 times did you mean browser cache or magnolia cache? BTW in 3.6 there is certain amount of cached items kept in memory if they are served often or recently so deleting the cache directory is not enough to flush the whole cache. I haven't had such problem with FF3 on linux working with various snapshots/milestones/RC whole day long. Cheers, Jan On Wed, 2008-07-16 at 21:21 +0200, Will Scheidegger wrote: > Hi Jan > > I'm confronted with the problem again - only this time a restart did > not resolve it! Here is the header for the request for the css file: > > http://localhost:8080/magnoliaAuthor/.resources/admin-css/admin-all.css > > GET /magnoliaAuthor/.resources/admin-css/admin-all.css HTTP/1.1 > Host: localhost:8080 > User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: > 1.9) Gecko/2008061004 Firefox/3.0 > Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Cookie: JSESSIONID=6B6534A0DC730C37D9871558F7A6D8B1 > If-Modified-Since: Wed, 16 Jul 2008 18:59:54 GMT > Cache-Control: max-age=0 > > HTTP/1.x 304 Not Modified > Server: Apache-Coyote/1.1 > Cache-Control: max-age=1216236937, public > Expires: Wed, 16 Jul 2008 19:35:37 GMT > Date: Wed, 16 Jul 2008 19:05:37 GMT > > After 3 restarts and 10x clearing the cache I'm finally able to go on > with my work again... > > will > > On 16.07.2008, at 18:30, Jan Haderka wrote: > > > Hi Will, > > no I haven't seen this (FF on Linux) but I heard some people have > > access > > issues when running on Leopard, which might or might not be related. > > Could you please try to get the response headers when you are getting > > back just an empty page? > > Thanks, > > Jan > > > > On Wed, 2008-07-16 at 18:16 +0200, Will Scheidegger wrote: > >> Dear Magnolias > >> > >> Before I create a JIRA issue I wanted to ask you if you have seen the > >> same effects: In Mag 3.6m3 every once in a while the admin css info > >> gets lost and the page displayes like this: > >> > >> http://www.fastforward.ch/personal/will/mag36_loosing_css.png > >> > >> Most of the time one does not notice it because the css is fetched > >> from the browser's cache, but when you clear the cache you end up > >> with > >> an unusable Magnolia. This _is_ a show stopper of corse. > >> > >> - When you try to load /cms/.resources/admin-css/admin-all.css in > >> these cases, all you get is an empty page (no error message, nothing) > >> - All the files in the magnolia cache folder are empty (don't know if > >> the admin css stuff get's cached in the first place) > >> - clearing the instance's "tmp" folder did not change anything eiter > >> => Restarting Magnolia solves the problem! > >> > >> Any ideas or experiences on your part? > >> > >> -will > >> > >> ---------------------------------------------------------------- > >> for list details see > >> http://documentation.magnolia.info/ > >> ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > > for list details see > > http://documentation.magnolia.info/ > > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/ > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
