I've tried to implement this solution, to have IIS handle CF 404 errors, but I 
can't seem to get it to work.  I have tried on my local XP Pro/IIS 5 and it 
works fine, but when following the steps and trying it on Win2k3/IIS 6, the 
requests are still passed off to CF Admin.

Any ideas, or has anybody else who has tried this experienced the same..???

-------------------------------------------------------------------------------------
Excerpt from http://www.coldfusionmuse.com/index.cfm/2006/9/7/site.by.site.404

The Fix
This is actually possible (though not intuitive). These instructions are for 
Win2003, IIS 6. Go to IIS and open your site properties. Click on the "home 
directory" tab and then click on the configuration button. If you have a 
typical setup you should see the Jrun wildcard entry in the bottom list box. 
Select this entry and click on "edit". There is a checkbox that says "verify 
that file exists". You might think that this means that IIS is supposed to 
verify that the wildcard dll exists. Nope... it means for IIS to make sure and 
verify that the file referenced in the request actually exists before throwing 
it to the Jrun. Like I said, it's not intuitive. Select this check box and 
click ok. Under the hood, IIS will verify that a file exists before handing it 
off to Coldfusion. If it does not exist it will call your 404 handler. Viola'!! 
... A site specific CF missing template handler. Not bad.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
CF 8 – Scorpio beta now available, 
easily build great internet experiences – Try it now on Labs
http://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_adobecf8_beta

Archive: 
http://www.houseoffusion.com/groups/CF-Server/message.cfm/messageid:6343
Subscription: http://www.houseoffusion.com/groups/CF-Server/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10

Reply via email to