Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- What's this mean please?
- Big Bill
August 19, 2008, 10:33 am
rate this thread
Putting my non-technical hat on again, what does the team make of this
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="expires" content="3600" />
I have to say, it appears on a site that the client's happy with but
looking at the code I'd say it's been cobbled together by people who
know how to cobble disparate bits of code together but can't actually
code themselves. I doubt it does anything but a second opinion doesn't
Re: What's this mean please?
Big Bill wrote:
The directive <meta http-equiv="Cache-Control" content="no-cache"/> and
its HTTP 1.0 brother <meta http-equiv="Pragma" content="no-cache" />
are telling the browser to fetch a fresh copy of the page each time
instead of using the local caching. Is there any reason to do this?
sometimes misguided individuals make such a request because they think
that their visit count is more important than the user's time. I would
delete it just in case it works -- because if it works it is bad for the
The directive <meta http-equiv="expires" content="3600" /> are telling
the browser and possibly some robots that the page expires in an hour.
This is universally ignored by search engines which have their own ways
of deciding how often to revisit.
The problem with these HTTP-EQUIV tags is that they are only seen
by agents that read the HTML (unless you are on a web server that
generates HTTP headers from the HTTP-EQUIV tags, as discussed in
the HTML 3.2 specification -- and you probably are not), and thus
miss things like caching proxy servers or firewalls.
- » Free people search engines! Check someone's background!
- — Next thread in » Search Engines