HTTP message headers Meta elements of the form <meta http-equiv="foo" content="bar"> can be used as alternatives to HTTP headers. For example, <meta http-equiv="expires" content="Wed, 21 June 2006 14:25:27 GMT"> would tell the browser that the page "expires" on June 21, 2006 at 14:25:27 GMT and that it may safely cache the page until then. The HTML 4.01 specification optionally allows this tag to be parsed by HTTP servers and set as part of the HTTP response headers,W3C Recommendation (December 24, 1999), HTML 4.01 Specification. W3.org, retrieved July 24, 2012 but no web servers currently implement this behavior.Stack Overflow, meta http-equiv – is it sent as part of an HTTP header, or does the client parse the body for meta tags?, from a London Web Standards tech talk. Instead, the user agent emulates the behavior for some HTTP headers as if they had been sent in the response header itself.
HTTP message headers Meta elements of the form <meta http-equiv="foo" content="bar"> can be used as alte,rnatives to HTTP headers. For e,xample, <meta http-equiv="expires" content="Wed 21 June 2006 14:25:27 GMT"> would tell the browser that the page "e,xpires" on June 21 2006 at 14:25:27 GMT and that it may safely cache the page until then. The HTML 4.01 specification optionally allows this tag to be parsed by HTTP servers and set as part of the HTTP response headers,W3C Recommendation (December 24, 1999) HTML 4.01 Specification. W3.org, retrieved July, 24, 2012 but no web servers currently implement this behavior.Stack Overflow meta http-equiv – is it sent as part of an HTTP header, or does the client parse the body for meta tags?, from a London Web Standards tech talk. Instead, the user agent emulates the behavior for some HTTP headers as if they had been sent in the response header itself.