What actually happens is mod_jrun passes the request to the jrun connector. If it is a cfm file or some other file that JRUN handles, then JRUN returns true, and handles the request. If it's a file that JRUN doesn't handle, then it returns false, and apache looks for another module that can handle the request.
You can see this in action if you enable the verbose logging. Russ > -----Original Message----- > From: Dinner [mailto:[EMAIL PROTECTED] > Sent: Monday, March 26, 2007 3:06 PM > To: CF-Talk > Subject: Re: Targetting an instance > > On 3/26/07, Dave W wrote: > > > I think the default web connector handles stuff a bit > > > differently- And you say CF, but you mean JRun, right? The > > > way I see it, and this is using apache for an example, but > > > with the default web connector, you add a "handler" for the > > > .cfm, .cfc, .jsp file types-- This means that if httpd sees > > > a request for fun.htm, it serves it directly, but if it sees > > > a request for fun.cfm, it lets JRun/CF "handle" it, and just > > > returns whatever CF returns. > > > > While the handler is there in httpd.conf, my experience with Apache and > > CF/JRun has been that JRun will be able to handle other requests, such > as > > requests for servlets (which aren't mapped to any file extension at > all). > > This indicates that JRun is able to examine every request, whether it > > matches one of the listed extensions or not. > > JRun's handling of requests is kinda separate from Apache HTTPD, as > it is a server in it's own right, so maybe that's part of the servelet > handling > and whatnot. > > Because if you turn off CF, HTTPD still serves out static content. But > try > for a extension handled by the jrun handler... and 500 error... > > I'm pretty sure that the JRun connector does some magic to get the request > evaluated in the context of the web root, vs. the CF instance- well, I > know > it does, otherwise there would be a bunch of entries in those config files > that Jochem talks about, and there isn't. There are no like, > "virtual" directories > for every place HTTPD serves CF content from (which can be anywhere, > with the JRun connector). > > How this all ties into clustering, I don't know. Very intertwined > tho, obviously, > as I'm getting into this stuff because I'm trying to run on jboss/tomcat, > not > for CF clustering (although tomcat has clustering... I wonder if anyone > has > done a comparison...) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273769 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
