Not cache html page

Html force page to not load from cache

Currently, as of July 2016, the HTML Standard, Section 7.9, Offline Web applications includes a deprecation warning: So does Using the application cache on Mozilla Developer Network that I referenced in 2012: See also Bug 1204581 — Add a deprecation notice for AppCache if service worker fetch interception is enabled. but I think it needs a more up to date answer because now there is a way to have more control of website caching.

DO not load a HTML page from cache

Those meta tags have an http-equiv attribute because they’re a document-level placeholder for items that should be in the HTTP response. Instead of sending requests for your bare resource, clients should be sending a «GET if not modified since X» request, and they should be set correctly in your header. Ask your host for reference on how to provide those «no cache» options.

See this exact duplicate of your question for more information, btw.

Also, a knowledge-utility basis, add a «Prices good until XXXX» in the content of your page. It’s a price list, so someone will print it out and think that it’s still a good price if you don’t have an indicator otherwise.

How To Force Reload Cached HTML Files, Use CTRL + SHIFT + R to reload. What chrome does is, when you load the page, it loads the external scripts. The first time you load the scripts, it caches it, so that it won’t have to load it every single time. To clear the cache, use CTRL SHIFT R. Check this out: Clear the cache in JavaScript. Share.

Force browser to clear cache

If this is about .css and .js changes, one way is to to «cache busting» is by appending something like » _versionNo » to the file name for each release. For example:

script_1.0.css // This is the URL for release 1.0 script_1.1.css // This is the URL for release 1.1 script_1.2.css // etc. 

Or alternatively do it after the file name:

script.css?v=1.0 // This is the URL for release 1.0 script.css?v=1.1 // This is the URL for release 1.1 script.css?v=1.2 // etc. 

You can check out this link to see how it could work.

Look into the cache-control and the expires META Tag.

Another common practices is to append constantly-changing strings to the end of the requested files. For instance:

Update 2012

This is an old question but I think it needs a more up to date answer because now there is a way to have more control of website caching.

In Offline Web Applications (which is really any HTML5 website) applicationCache.swapCache() can be used to update the cached version of your website without the need for manually reloading the page.

This is a code example from the Beginner’s Guide to Using the Application Cache on HTML5 Rocks explaining how to update users to the newest version of your site:

// Check if a new cache is available on page load. window.addEventListener('load', function(e) < window.applicationCache.addEventListener('updateready', function(e) < if (window.applicationCache.status == window.applicationCache.UPDATEREADY) < // Browser downloaded a new app cache. // Swap it in and reload the page to get the new hotness. window.applicationCache.swapCache(); if (confirm('A new version of this site is available. Load it?')) < window.location.reload(); >> else < // Manifest didn't changed. Nothing new to server. >>, false); >, false); 

See also Using the application cache on Mozilla Developer Network for more info.

Update 2016

Things change quickly on the Web. This question was asked in 2009 and in 2012 I posted an update about a new way to handle the problem described in the question. Another 4 years passed and now it seems that it is already deprecated. Thanks to cgaldiolo for pointing it out in the comments.

Currently, as of July 2016, the HTML Standard, Section 7.9, Offline Web applications includes a deprecation warning:

This feature is in the process of being removed from the Web platform. (This is a long process that takes many years.) Using any of the offline Web application features at this time is highly discouraged. Use service workers instead.

So does Using the application cache on Mozilla Developer Network that I referenced in 2012:

Deprecated
This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. Do not use it in old or new projects. Pages or Web apps using it may break at any time.

See also Bug 1204581 — Add a deprecation notice for AppCache if service worker fetch interception is enabled.

How to clear cache memory on load of HTML page?, 1 Answer. This meta code should work with most browsers for web content. However, for resource files (javascript, images, css) your mileage may vary. Most cache busting strategies involve changing the name of your resource files (perhaps dynamically) or using Apache rewrite rules to pretend that the …

Prevent caching of HTML page [duplicate]

The Codesnippet you showed makes the browser load the website everytime it accesses it, which is useful if you perform frequent updates, but still have a static page.

In case you want it to perform live updates , like it does for example in a (g)mail account, you need to make it refresh (parts of the page) itself. Use Javascript in this case, like it is shown in this question or an ajax call.

The values you have there are OK, but meta http-equiv is highly unreliable. You should be using real HTTP headers (the specifics of how you do this will depend on your server, e.g. for Apache).

Html — how to force page not to load from cache if there, how to force page not to load from cache if there are changes in page. I have a site with advertisements and so the user is able to change his advertisement. But if the user goes to his own advertisement the page is the same, because the page loads from the browser cache. I can use a meta tag that tels …

Force browser to not use cache when requested for file using anchor tag

I’ll add as an answer. Try adding a random number to the query part of the href:

As per my own comment for one of the answers:

According to wikipedia I can set the response header parameter: Cache-Control: no-cache

After receiving a response with this header, the browser will not cache this data anymore.

How to force a browser to refresh a cached version of a, As a result, when a person visits the site, they often make no attempt to even request the page. The browser just loads the HTML from cache. This website is about to get a major update, and I would like for users to be able to see it. Is there a way for me to force a user to actually re-request the webpage? I fear …

Источник

Disable browser caching with meta HTML tags

The correct minimum set of headers that works across the most important browsers:

Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires: 0

Web Pages (HTML)

For the Web Pages (HTML) add the following tags to the page(s) you want to keep browsers from caching (the code must be in the section of your page, for example right after tag):

 http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />  http-equiv="Pragma" content="no-cache" />  http-equiv="Expires" content="0" />

.htaccess (Apache)

IfModule mod_headers.c> Header set Cache-Control "no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires 0 IfModule>

Java Servlet

response.setHeader("Cache-Control", "no-cache, no-store, must-revalidate"); response.setHeader("Pragma", "no-cache"); response.setDateHeader("Expires", 0);

PHP

header('Cache-Control: no-cache, no-store, must-revalidate'); header('Pragma: no-cache'); header('Expires: 0');

ASP

Response.addHeader "Cache-Control", "no-cache, no-store, must-revalidate" Response.addHeader "Pragma", "no-cache" Response.addHeader "Expires", "0"

ASP.NET

Response.AppendHeader("Cache-Control", "no-cache, no-store, must-revalidate"); Response.AppendHeader("Pragma", "no-cache"); Response.AppendHeader("Expires", "0");

Ruby on Rails

response.headers['Cache-Control'] = 'no-cache, no-store, must-revalidate' response.headers['Pragma'] = 'no-cache' response.headers['Expires'] = '0'

Python on Flask

resp.headers["Cache-Control"] = "no-cache, no-store, must-revalidate" resp.headers["Pragma"] = "no-cache" resp.headers["Expires"] = "0"

Google Go

responseWriter.Header().Set("Cache-Control", "no-cache, no-store, must-revalidate") responseWriter.Header().Set("Pragma", "no-cache") responseWriter.Header().Set("Expires", "0")

Categories & Tags

Источник

Запрет кэширования страницы на HTML, PHP, htaccess

Порой, бывает необходимо запрещать браузеру кэшировать страницу, так как информация на ней обновляется каждый раз. Это может быть генерация данных, соответственно выбранным фильтрам или другой контент, который каждый раз создается по-новому. Одним словом, бывают моменты, когда необходимо запретить коварной программе кэшировать страницу. Сегодня, мы узнаем, как реализовать это разными способами, с помощью PHP или HTML или .htaccess.

Запрет кэширования страницы на HTML

Сделать это можно с помощью мета тегов. Сейчас мы разберем разные варианты запрета на кэширование.

Запрет на кэширование браузером и прокси-сервером

Запрет кэширования страницы, только браузером

Установка кэширования на определенное время, для браузера

С помощью кода ниже, мы можем сообщить браузеру, сколько хранить документ в кэше. После чего, кэш будет обновлен.

Установка кэширования на определенное время, для прокси-сервера

Практически, то же самое, что и в предыдущем коде, только указание стоит конкретно для прокси-сервера.

Запретить кэширование страницы с помощью PHP

Практически, все тоже самое, что в случае с HTML, только информацию будем выводить через header заголовки. Вот, как реализовать абсолютный запрет на кэш:

Также, можно разрешать кэшировать на определенное время. Например, разрешим кэширование только на 1 час.

Запретить кэширование страницы с помощью .htaccess

Для простоты реализации идеи, можно все сделать на уровне конфигураций сервера Apache. Перед этим, нам нужно убедиться в том, что необходимые модули находятся в рабочем состоянии. Открываем конфигурационный файл Apache и наблюдаем следующую картину:

LoadModule expires_module modules/mod_expires.so LoadModule headers_module modules/mod_headers.so . AddModule mod_expires.c AddModule mod_headers.c

Теперь в файле .htaccess, собственно запрещаем кэшировать выводимые данные. Как нам известно, .htaccess файл будет распространяться на директорию, в которой лежит, и на все субдиректории.

# Заголовок Cache-Control Header append Cache-Control "no-store, no-cache, must-revalidate" # Заголовок Expires ExpiresActive On ExpiresDefault "now" 

Важно заметить, что полный запрет кэширования, повышает нагрузку на сервер. Поэтому, играйтесь с этим осторожно! А лучше, установите определенное время, на которое можно кэшировать документы. Например, установим кэширование на 1 час:

# Заголовок Cache-Control Header append Cache-Control "public" # Заголовок Expires ExpiresActive On ExpiresDefault "access plus 1 hours" 

Заключение

Это все известные для меня способы запрета на кэш. Если знаете что-то новенькое, просьба поделиться в комментариях. Надеюсь, статья была полезной, если это так, вас не затруднит поставить +1 и поделиться ею в социальных сетях.

Источник