And, as a side, you can use an application level CF request 404 handler by using the onMissingTemplate() method in Application.cfc. This only works for requests to CF processed resources, by template name (a directory call will just die).
https://learn.adobe.com/wiki/display/coldfusionen/onMissingTemplate Steve 'Cutter' Blades Adobe Community Professional Adobe Certified Expert Advanced Macromedia ColdFusion MX 7 Developer ____________ http://cutterscrossing.com Co-Author "Learning Ext JS 3.2" Packt Publishing 2010 https://www.packtpub.com/learning-ext-js-3-2-for-building-dynamic-desktop-style-user-interfaces/book "The best way to predict the future is to help create it" On 9/18/2013 5:33 AM, Russ Michaels wrote: > In the cfadmin youbyou set the missing and error templates as /filename.cfm > and put it in the root of the site. > It seems that with cf10/Apache if it doesn't find a file in the expected > location it will look in cf internal doc root instead, so u need to clear > out that folder. > > Iis 404 template wont work for cfm files because cf processes the request > first to determine if it exists. > > Russ Michaels > www.michaels.me.uk > cfmldeveloper.com > cflive.net > cfsearch.com > On 17 Sep 2013 21:27, "Money Pit" <[email protected]> wrote: > >> I've seen and dealt with plenty of CF10 404 issues since my install >> yesterday, but this appears to be a new one: >> >> This is my first CF10 installation. I am running with Update 11 in place. >> Win2k8 R2/64bit. >> >> 1. CF Admin's missing template handler residing in the cfusion wwwroot is >> nonfunctional. The site wide template handler in the same location works >> fine. >> >> 2. The err404.cfm 404 handler I have executing via IIS works, but get >> this... the url is supposed to be relative to *site* root, right? In IIS, >> on a site that is not the default web site, where CF is using its default >> web root location and IIS is using an entirely different one (nonstandard >> on a different folder tree) *the IIS 404 page is executing from the CF web >> root*. That shouldn't be possible. Took me hours to realize it was >> happening. I have ensured that I have unique filenames in place and can't >> see any reason why IIS - in this one case - treats the 'site root' as the >> default cf webroot location. Here is my missing template handler, kept >> simple: >> >> <cfheader >> statuscode="404" >> statustext="Not Found"> >> <h1>404</h1><p>Page not found</p> >> <cfoutput>#now()#</cfoutput> >> >> There's more. The IIS missing template handler works fine for non-CF >> pages. For foo.htm I get display and 404 header as expected. For foo.CFM >> I get... nothing (with a 200 status code). I have IIS doing failed request >> traces and for foo.htm I get a failed url of >> >> http://[domain]:80/foo.htm >> >> but foo.cfm's request trace gives the failed url of >> >> http://[domain]:80/jakarta/isapi_redirect.dll >> >> Anyone? I have been all over stack overflow and it has helped me through >> other issues (adding /jakarta virtual directory etc.) but this has me >> stumped. >> >> >> -- >> --m@Robertson-- >> Janitor, The Robertson Team >> mysecretbase.com >> >> >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:356811 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
