Working around Cold Fusion Developers Licensing issues
Posted October 1st, 2008 by chrisI have fond memories of this “Rightous Hack”.
Back a few years ago, I was installing the cold fusion developers edition on a W2K3 dev server in IIS. I soon found out that Coldfusion 7 Developers edition provides limitations by only letting two unique IP’s and localhost connect to the coldfusion site.
With some help from a very good mentor of mine, we set up the IIS sites to answer for an arbitrary port. After that we install Apache 2.2 on the machine, and set up virtual hosts to answer for the site names, then used mod_proxy to pass all connections to the high ports serving the content in IIS. All connections to IIS appear to be coming from localhost, so CF developement server didn’t bitch.
Doesn’t change the fact that Cold Fusion is. Well if you can’t say anything nice, don’t say anything at all. At least its fairly reliable.
An update,: so I suppose you want some know-how, so here we are.
1. Get your cold fusion site all up and running and happy. I have on up and running with IIS.
2. Change this site to listen on a high port, freeing up port 80 for apache. Stop the default site if necessary.
- Make port 80 available to apache.
3. Install apache2. You can download here.
4. Enable mod_proxy_http and mod_proxy at the minimum. I also needed and enabled mod_vhost_alias.
5. Configure vhosts [in "extras" folder] to your vhost specifications. Here is mine. Note that as far as I know, it’s bad to turn on ProxyRequests without security.
I belive you can turn it off. Since this is an internal developement site only, and I was in a hurry, I turned it on.
Note that ProxyPreserveHost is off, making all requests look like they come from 127.0.0.1.
Tags: ColdFusion, IIS
Filed under:Fail, Rightous Hacks
Leave a Reply
You must be logged in to post a comment.