Pitney Bowes MapXtreme - Manual (Page 98)

Chapter 5: Web Applications, Controls, and Tools
HTML/XHTML Validation Issues
MapXtreme v7.1 98 Developer Guide
To specify a cache option, modify your web.config file to point to the key
MapInfo.Engine.Session.Cacheability, as follows.
<appSettings>
<add key="MapInfo.Engine.Session.Cacheability"
value="private"></add>
</appSettings>
Caching Expiration
You can also set an expiration date for your cached tiles. Set an expiration date when the data in the
tile needs to be refreshed. By expiring tiles, users of your application will receive only the most
up-to-date information displayed.
To set the cache expiration, add a key to the web.config file, as follows:
<appSettings>
<add key="MapInfo.Engine.Session.CacheExpires"
value="4/1/2010"></add>
</appSettings>
The value can be any string that can be successfully parsed by Microsoft’s DateTime.Parse(String)
method.
Note that Microsoft limits the expiration date to one year. Any date beyond one year will not be
honored.
HTML/XHTML Validation Issues
If you create a MapXtreme web application and run the resulting HTML through a validator service,
you might see the following validation error, depending on what version DOCTYPE tag you use:
value of attribute "ID" invalid. "_" cannot start name
This validation error is in reference to a hidden field with the attribute
id="__VIEWSTATE"
Server Specifies that the response is cached only at the origin server.
Similar to the NoCache option. Clients receive a Cache-Control: no-
cache directive but the document is cached on the origin server.
Equivalent to ServerAndNoCache.
ServerAndNoCache Applies the settings of both Server and NoCache to indicate that the
content is cached at the server but all others are explicitly denied the
ability to cache the response.
ServerAndPrivate Indicates that the response is cached at the server and at the client
but nowhere else. Proxy servers are not allowed to cache the
response.