We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Retrieve from cache or server: what is Firefox's logic

  • 2 réponses
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par DavyStokes

DavyStokes
DavyStokes
more options

I clicked on a hyperlink to visit a web site that I had not visited for a couple of months. Firefox showed me the page as it was when I last visited it. I pressed F5 and the page updated to the latest version. I don't seem to have this problem with other websites; just this one. Does anybody understand the logic Firefox uses when determining whether to display a page from the cache or to get the latest page from the web server?

Using Firefox 10; Windows XP

I clicked on a hyperlink to visit a web site that I had not visited for a couple of months. Firefox showed me the page as it was when I last visited it. I pressed F5 and the page updated to the latest version. I don't seem to have this problem with other websites; just this one. Does anybody understand the logic Firefox uses when determining whether to display a page from the cache or to get the latest page from the web server? Using Firefox 10; Windows XP

Solution choisie

The site may not be sending an ETag header in the response headers or otherwise send info that makes Firefox think that the cached data has expired.

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Solution choisie

The site may not be sending an ETag header in the response headers or otherwise send info that makes Firefox think that the cached data has expired.

DavyStokes
DavyStokes Auteur de la question
more options

Thank you cor-el. The first link mnot is particularly useful. But what I have learnt is that caching is a black art. The logic is influenced by the browser logic, the browser cache size, the web servers caching rules and the html on the page. Impossible for the user to control; very difficult for the web page author. So even if I were to understand Firefox's logic it would not help me much.