Hmm.. it didn't work. I found the jsp mapping, chose Edit and selected "Verify that file exists".
Still shows the JRun error. Restarted the service and even the server to see if that was required to activate it. Nope - still get standard JRun 404 message. I don't mind if this "breaks" things. Currently this is a server serving one purpose - to take redirects from other systems while they're "down". This is temporary, so when done, I will undo the changes and get it back up and running as a (dev) CF server. Should I also remove (or modify??) the executable path of C:\JRun4\lib\wsconfig\jrun_iis6.dll? Any help/advice on getting JRun NOT to respond, and get my custom 404s working (which they do for all other requests) is much appreciated. Thanks! On 3/17/2010 9:33 PM, Dave Watts wrote: > >>>> In your IIS settings, there should be an option for the ISAPI filter or >>>> extension mapping called "Verify that file exists." >>>> >>> This will break various things in CF, however - charting, CFIMAGE, >>> RDS, Flash Remoting. >>> >> Will just enabling the Verify that file exists setting in IIS break things >> or were you just referring to using a 404.cfm file? >> > Yes, just enabling the "verify that file exists" option will break > these things, because IIS will then throw 404s for specific legitimate > URL patterns that CF recognizes. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:331863 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
