Using META HTTP-Equiv tags

An alternative to the Cache-Control HTTP header is to use META HTTP-Equiv tags. These tags produce the same result as the equivalent HTTP header when used within your channel pages and are processed by the M-Business Sync Server and displayed in M-Business Client. We strongly recommend that you use HTTP headers instead of META HTTP-Equiv tags if at all possible. If you are unable to use HTTP caching headers because your server does not support them or you do not have the necessary administrative privileges to enable them, you can use META HTTP-Equiv tags as an alternative method to specify caching on your pages.

Caution

Proxy servers generally ignore META HTTP-Equiv tags, and some browsers also do not support these tags. If you serve the same content to both your M-Business Sync Server and other Web clients such as desktop browsers, by using META HTTP-Equiv tags you may not get the same benefits of caching for these other clients that you would if you used HTTP headers.

META HTTP-Equiv tags have the following form:

<META HTTP-EQUIV="name" CONTENT="content">

Where name is the name of the HTTP header, and content is the parameter string that you would use with the HTTP header.

For example, the following Cache-Control header:

Cache-Control: max-age=604800

Would translate to the following META HTTP-Equiv tag:

<META HTTP-EQUIV="Cache-Control" CONTENT="max-age=604800">

And the following Expires header:

Expires: Tue, 25 Jan 2000 10:30:00 GMT

Would translate to the following META HTTP-Equiv tag:

<META HTTP-EQUIV="expires" CONTENT="Wed, 26 Feb 1997 08:21:57 GMT">
Note

Like all META tags, META HTTP-Equiv tags must be placed in the HEAD section of the page.