I don't think these will be issues in this instance. I also meant to try using the wildcard dll specifically for .cfm requests instead of cf-iis6.dll or whatever, but now that I'm thinking about it I'm not sure if I actually did that.
I did try without the wildcard. That allowed .HTML files to work but .cfm still didn't work. Andrew. On 2010-07-10, at 13:11, Dave Watts <[email protected]> wrote: > >> Instead of using the isapi as a wildcard, try having it be the handler for >> .cfm files and the static files won't be handled by the dll. I >> don't know if you would need other extensions as well, but you can set those >> up the same way. > > That will fix this problem, but it will introduce other problems. CF > does rely on URL patterns that don't necessarily correspond with > extensions or physical locations that exist (CFIMAGE, RDS, etc) and > those rely on the use of a filter rather than an extension handler. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > http://training.figleaf.com/ > > Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on > GSA Schedule, and provides the highest caliber vendor-authorized > instruction at our training centers, online, or onsit > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335238 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
