Thanks for the explanation, Dave. It appears on linux at least the JRun pre-filter is detecting *.cfm* as being a CF file, and then somewhere else (perhaps in the post filter?) determining that it's not and throwing an error..
In the end it doesn't really matter. One nice side effect is that if you accidentally save a file as test.cfm.save (or any other temporary extension), it cannot be read by the server in cleartext. Terry > > Wow, I never realized that Jrun looked at every HTTP request. Isn't > that the whole point of AddHandler? To > > tell Apache what file types to hand off to Jrun? Do the > "AddHandler" statements do anything then? > > Well, I'm not entirely sure if they do anything. I'm not as familiar > with Apache internals as I am with IIS. > > Here's how things work in IIS: when you install the web server > connector, it configures an ISAPI module (much like an Apache module, > I guess) that hooks into the IIS processing pipeline in two places - > at the very beginning (an ISAPI filter) and at the very end (an ISAPI > extension). The filter passes all requests to JRun regardless of the > URL pattern, and then JRun accepts or rejects them based on the URL > patterns it's configured to use. If JRun rejects the request, it gets > passed back to IIS for normal handling. The ISAPI extension, on the > other hand, is only invoked based on specific file extensions. By > default, both would be configured, but there would be specific > use-cases where you might choose to disable the filter (by enabling > the "check that file exists" option in IIS which requires that IIS > itself process the file first, for example). Disabling the filter > would also cause some features not to work, as some "magic" URL > patterns that CF executes don't actually exist (/CFIDE/Main/ide.cfm > for RDS, the URL patterns for CFCHART and CFIMAGE, etc). > > At least, this is how things used to work in IIS - it's a bit > different now, as CF installs an ISAPI wildcard extension instead of > a > filter. But the wildcard extension, like the filter before it, sends > all requests to JRun. > > So, assuming that the filtering functionality is working in Apache, > my > guess is that the AddHandler statements aren't doing anything for > those requests. > > This is why some people configure CF to have a context root other > than > "/". For example, on the Adobe site, CF files all have this URL > pattern somewhere within the URL: "/cfusion". That's the context root. > > By having this non-standard context root, the web server can directly > process any URLs without that pattern. This will improve performance > - > not that much, as far as I can tell, but a little. > > 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 onsi ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-linux/message.cfm/messageid:4570 Subscription: http://www.houseoffusion.com/groups/cf-linux/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-linux/unsubscribe.cfm
