Thanks! Dave Watts <[EMAIL PROTECTED]> wrote:> (Can't configure MX to work on a lower level than a web site)
You can, if you're using IIS, by manually doing what the wsconfig utility would do. In the Internet Service Manager console, you can create a virtual application, which is just a virtual directory with its own application settings. You can then create the necessary extension mappings within that virtual application. However, I don't think that's a very good idea in general; you're better off using MX for the entire virtual server. > Before installing MX though, I created a new web site, > assigning it to a different http port, and gave that > site a new home directory, then told MX that was my > home directory for the site MX was to work with. Of > course, instead of using a different port number, I > could have assigned the second web site another IP, > but I didn't want to bother with getting a static > IP from the admin. Or, you could just bind them all to the same IP address and port, and use host-header names to differentiate them. To make that work, you'd either need to be able to add CNAME entries to your DNS server, or you can just edit your HOSTS file if it's for local development use. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
