<CFCACHE ACTION="action" PROTOCOL="protocol name" TIMEOUT="timeout date-time" DIRECTORY="directory name for map file" CACHEDIRECTORY="directory name for cached pages" EXPIREURL="wildcarded URL reference" PORT= "port-number">You can use CFCACHE for simple URLs and URLs that contain URL parameters.
Optional. Specifies one of the following:
See the Usage section for more information.
Optional. Specifies the protocol used to create pages from cache. Specify either HTTP:// or HTTPS://. The default is HTTP://.
Optional. DateTime that specifies the oldest acceptable cached page. If the cached page is older than the specified datetime, ColdFusion refreshes the page. By default, ColdFusion uses all cached pages. For example, if you want a cached file to be no older than 4 hours, code the following:
Optional. Used with ACTION=FLUSH. Specifies the fully qualified path of a directory containing the cfcache.map to be used when ACTION=FLUSH. The default is the directory of the current page.
Optional. Specifies the fully qualified path of the directory where the pages are to be cached. The default is the directory of the current page.
Optional. Used with ACTION=FLUSH. EXPIREURL takes a wildcarded URL reference that ColdFusion matches against all mappings in the cfcache.map file. The default is to flush all mappings. For example, "foo.cfm" matches "foo.cfm"; "foo.cfm?*" matches "foo.cfm?x=5" and "foo.cfm?x=9".
Optional. The port number of the web server from which the page is being requested. The port number defaults to 80. The port number is useful because the CFCACHE code calls CFHTTP. If the port number is specified correctly in the internal call to CFHTTP, the URL of each retrieved document is resolved to preserve links.
In its simplest form, all you need to do is code
With the ACTION attribute, you can specify server-side caching, browser caching, or a combination of server-side and browser caching. The advantage of browser caching is that it takes no ColdFusion resources because the browser stores the pages in its own cache, thus, improving performance. The advantage of using a combination of the two forms of caching is that it optimizes performance; if the browser cache times out, the server can retrieve the cached data from its own cache.
In addition to the cached files themselves, CFCACHE uses a mapping file to control caching. It is named cfcache.map and uses a format similar to a Windows INI file. The mapping of a URL with parameters is stored as follows. Assume a directory "c:\InetPub\wwwroot\dir1" that has a CFM file called "foo.cfm", which can be invoked with or without URL parameters. The cfcache.map file entries for foo.cfm will look like this:
[foo.cfm] Mapping=C:\InetPub\wwwroot\dir1\CFCBD.tmp SourceTimeStamp=08/31/1999 08:59:04 AM [foo.cfm?x=5] Mapping=C:\InetPub\wwwroot\dir1\CFCBE.tmp SourceTimeStamp=08/31/1999 08:59:04 AM [foo.cfm?x=9] Mapping=C:\InetPub\wwwroot\dir1\CFCBF.tmp SourceTimeStamp=08/31/1999 08:59:04 AM
The cfcache.map file in a given directory stores mappings for that directory only. Any time the timestamp of the underlying page changes, ColdFusion updates the cache file for that URL only. ColdFusion uses the SourceTimeStamp field to determine if the currently cached file is up to date or needs to be rebuilt.
You can refresh the cache in the following ways:
Note the following regarding CFCACHE:
<CFSETTING SHOWDEBUGOUTPUT="NO">
.
PROTOCOL="http://"
. If you need to use SSL, you must run ColdFusion as a desktop application. Please note, however, Allaire strongly recommends that you run the ColdFusion Server as a service. For more details about using SSL, see Knowledge Base article #1096 at http://www.allaire.com/Support/KnowledgeBase/SearchForm.cfm.