>I have apache on the FE web servers, and also apache on the individual CF >servers, and I have apache on the CF servers connecting through the jrun >connector to CF. I am proxying requests from the FE web servers to the >backend CF servers through the loadbalancer, which stays in complete >control. What I did was put in some restrictions in jrun.xml or one of the >other xml files to restrict it to 127.0.0.1, so that the local jrun >connector only connects to the local JRUN instance. > >So basically I think what you need to do in your set up is install apache >locally on the CF servers and proxy through that instead of using the built >in web server. Apache has no problems with UNC paths. > >Russ
Brilliant!!! I may need to stick with IIS on the internal side for the Authentication aspects but as for our Dotcom side I would rather run Apache and probably will. Hmmmm maybe I can run apache on Intranet, trying to figure out in this scenario who is going to be checking the Users credentials I believe IIS still does then proxies to get the content. Thanks Russ for helping me out of the fog I managed to talk myself into!! ~Eric ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:10/messageid:6028 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10
