(See below)

On 8/2/12 9:50 PM, James Ducker wrote:
Second that. If you can version the filenames that's definitely the
most sure-fire way to make sure users don't cache old copies.


On 3 August 2012 14:39, Emmanuel Negri <nna...@gmail.com
<mailto:nna...@gmail.com>> wrote:

    Sometimes a random query string does not work.

    Changing the filename itself works 100% of the time.

    Eg. style-<scm-revision-number>.css


    On 03/08/2012, at 1:25 PM, James Ducker <james.duc...@gmail.com
    <mailto:james.duc...@gmail.com>> wrote:

    Append some junk querystring to the end of the URL, like
    <http://example.com/index.html?20120803132400>. Every time it changes,
    stuff will be refreshed. Wouldn't really recommend doing it for
    regular pages because it makes the URLs look messy, but if you're
    trying to refresh scripts or images, go nuts.


    On 21 July 2012 03:22, Rob Crowther <robe...@boogdesign.com
    <mailto:robe...@boogdesign.com>> wrote:

        On 20/07/2012 17:47, coder wrote:

            How can I make a web page appear as the latest version in all
            i.e., perform a cache bypass?  And I don't mean for me - I
            mean for all
            visitors to the page?  Is it possible?

        Once it's cached in the browser there's not much you can do about
        it, the browser will store the cache settings at the time when it
        cached the page and if those settings say "don't check again for a
        month" then, generally, it won't.

        If you want the page to never be cached then you need to set the
        expiry header.  With Apache servers this is quite straightforward
        and can usually be done in the directory's .htaccess file:

        ExpiresByType text/html                 "access plus 0 seconds"

        This is example was take from HTML5 BoilerPlate:



You may be interested in this automated way of doing it:



List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org

Reply via email to