Ah. I forgot that it's only in cfoutput you need to worry aobut ##s. Duh! The idea about the tracker link was to insert it in the .html pages, vs. changing the .html pages to .cfm.
Thus, funpage.html has a img link to "tracker.cfm", so each time the ..html page is loaded, there is a request to the tracker page. But John has a good point (maybe already addressed): Why not use a stat program? There are plenty out there that will parse the server logs and give nifty graphs and whatnot for all resources, cf or no. Is that not an option? :den On 9/2/06, Pete Ruckelshaus <[EMAIL PROTECTED]> wrote: > > There are links "in the wild" that are HTML pages that need to be > processed, so if they were changed to .cfm pages, it would generate > 404's. As far as #'s, etc., that would only be an issue for content > that's inside cfoutput tags, which they won't have -- I'm mainly > needing the functionality found in the application.cfm file, which > contains the "sniffer" code. > > Pete > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251934 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
