cfcache
Stores a copy of a page on the server and/or client computer, to improve page rendering performance. To do this, the tag creates temporary files that contain the static HTML returned from a ColdFusion page.
Use this tag if it is not necessary to get dynamic content each time a user accesses a page.
You can use this tag for simple URLs and for URLs that contain URL parameters.
<cfcache
action = "cache|flush|clientcache|servercache|optimal"
directory = "directory name"
expireURL = "wildcarded URL reference"
password = "password"
port = "port number"
protocol = "http://|https://"
timespan = "value">
username = "username">
cfflush, cfheader, cfhtmlhead, cfsetting, cfsilent
ColdFusion MX:
- Deprecated the cachedirectory and timeout attributes. They might not work, and might cause an error, in later releases.
- Added the timespan attribute.
- Changed how pages are cached: the default action attribute value, cache, caches a page on the server and the client. (In earlier releases, this option cached a page only on the server.)
- Changed the source of the protocol and port values: the default protocol and port values are now taken from the current page URL. (In earlier releases, they were "http" and "80", respectively.)
- Changed how session state is handled when caching a page: this tag can cache pages that depend on session state, including pages that are secured with a ColdFusion login. (In earlier releases, the session state was cleared when caching the page, causing authentication to be lost.)
- Changed how files are cached: this tag uses a hash() of the URL for the filename to cache a file. (In earlier releases, ColdFusion used the cfcache.map file.)
|
Attribute |
Req/Opt |
Default |
Description |
|---|---|---|---|
|
action |
Optional |
cache |
|
|
directory |
Optional |
cf_root/cache |
Absolute path of cache directory. |
|
expireURL |
Optional |
Flush all cached pages |
Used with action = "flush". A URL reference. ColdFusion matches it against the mappings in the specified cache directory. Can include wildcards, for example: "*/view.cfm?id=*". |
|
password |
Optional |
|
A password. Provide this if the page requires authentication at the web-server level. |
|
port |
Optional |
The port for the current page |
Port number of the web server from which the URL is requested. In the internal call from cfcache to cfhttp, ColdFusion resolves each URL variable in the page; this ensures that links in the page remain functional. |
|
protocol |
Optional |
The current page protocol |
Protocol that is used to create URL from cache.
|
|
timespan |
Optional |
Page is flushed only when cfcache action = "flush" is executed |
The interval until the page is flushed from the cache.
|
|
username |
Optional |
|
A username. Provide this if the page requires authentication at the web server level. |
Use this tag in pages whose content is not updated frequently. Taking this action can greatly improve the performance of your application.
The output of a cached page is stored in a file on the client browser and/or the ColdFusion server. Instead of regenerating and downloading the output of the page each time it is requested, ColdFusion uses the cached output. ColdFusion regenerates and downloads the page only when the cache is flushed, as specified by the timespan attribute, or by invoking cfcache action=flush.
To enable a simple form of caching, put a cfcache tag, specifying the timespan attribute, at the top of a page. Each time the specified time span passes, ColdFusion flushes (deletes) the copy of the page from the cache and caches a new copy for users to access.
You can specify client-side caching or a combination of client-side and server-side caching (the default), using the action attribute. The advantage of client-side caching is that it requires no ColdFusion resources; the browser stores pages in its own cache, improving performance. The advantage of combination caching is that it optimizes server performance; if the browser does not have a cache of the page, the server can get data from its own cache. (Adobe recommends that you use combination caching, and do not use server-side only caching.)
If a page contains personalized content, use the action = "clientcache" option to avoid the possibility of caching a personalized copy of a page for other users.
Debug settings have no effect on cfcache unless the application page enables debugging. When generating a cached file, cfcache uses cfsetting showDebugOutput = "no".
The cfcache tag evaluates each unique URL, including URL parameters, as a distinct page, for caching purposes. For example, the output of http://server/view.cfm?id=1 and the output of http://server/view.cfm?id=2 are cached separately.
The cfcache tag uses the cfhttp tag to get the contents of a page to cache. If there is an HTTP error accessing the page, the contents are not cached. If a ColdFusion error occurs, the error is cached.
For more information, see "Caching ColdFusion pages that change infrequently" 34 in the ColdFusion Developer's Guide.
<!--- This example produces as many cached files as there are URL parameter permutations.
You can see that the page is cached when the timestamp doesn't change.--->
<cfcache
timespan="#createTimeSpan(0,0,10,0)#">
<body>
<h3>This is a test of some simple output</h3>
<cfoutput>
This page was generated at #now()#<br>
</cfoutput>
<cfparam name = "URL.x" default = "no URL parm passed">
<cfoutput>The value of URL.x = # URL.x #</cfoutput>