On May 2, 2012, at 11:31 AM, Peter Gutbrod wrote: > Is it possible to set the fusebox page option in a4d.ini only for certain > virtualhosts, while others don't use fusebox, aka serve any .a4d file?
I no longer have a working version, but for years we ran both fusebox circuits and non fusebox circuits (old stuff that was not coverted). What is in the .ini file (fusebox page) forces everything through index.a4d. If you don't set it, any executable will work. If it is fusebox circuit, just make sure the index.a4d is a fusebox version. I checked the last version of the ini file and fusebox page = and default page = We had several virtual host (all fusebox), but still had a little left that was not fusebox. It was controlled by settings in the On Request handler in Active4D.a4l and a unique drivers. Setting the fusebox page just protects you from direct execution of a file, unless you white list it. If the non fusebox stuff goes through a master controller (e.g., default.a4d), you could white list default.a4d. If you have a bunch of drivers, just don't set it. I'm sure this is not the preferred way, but I couldn't convert everything to fusebox at one time and it worked fine for us. Steve Alex _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
