Technically, you can set your webserver to check for the existence of files before trying to send them to CF. You can then also set a CF page as your 404 handler for the folder or site (e.g. in .htaccess for Apache), thus getting better granularity than in the single serverwide missing template handler.
The downside to this is that servlet filters (like CFCHART graphing) break until you manually place dummy files into the filesystem to get past the fact that the location specified in the URL now causes a 404 rather than being passed directly to CF. On 4/22/06, Denny Valliant <[EMAIL PROTECTED]> wrote: > I had thought it might be "trappable", but from what I gathered the only > thing you > can do is set the missing template handler in the cf admin. > > On 4/19/06, Mike Garner <[EMAIL PROTECTED]> wrote: > > > > Anyone know if it's possible to catch this exception (when a CFM page is > > called that doesn't exist) in the application without using the Missing > > Template Handler? I was hoping to handle this in the application.cfc, but > > it looks like this error is thrown before it ever hits the application.cfc -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238485 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
