Hi *,

On Fri, Apr 29, 2011 at 4:49 PM, Nino Novak <[email protected]> wrote:
>> [empty page displayed instead of contents]
>
> Might have been a problem with caching. I just happened to have the same
> problem with http://wiki.documentfoundation.org/QA/de - one browser
> showing an empty page (no html) but a second browser displayed the page
> completely without problems.
>
> Looking at the http headers, the server response showed a
>  HTTP/1.1 304 Not Modified
> header.

But then it is a browser bug as it has been stated that the browser
cache has been cleared.
And when the browser doesn't have a copy of the file anymore, then it
doesn't make sense to ask the server whether the cached copy is still
current.

So the browser's cache has not been cleared...

(clearing the cache usually isn't necessary btw, using a forced
refresh does the trick in most browsers as well - in chromium it is
<shift>+reload, but in other browsers it might be <ctrl>+reload. Also
chromium apparently has two levels of cache. With the first
shift-reload, it does fetch a new copy of the html, but external data
such as css or images still come from the browser cache - thus to be
sure force-reload twice if something looks wrong.
If it then still doesn't display properly, clear the cache.

ciao
Christian

-- 
Unsubscribe instructions: E-mail to [email protected]
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/website/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to