Women in Technology

Hear us Roar



Article:
  ColdFusion MX on Mac OS X, Part 3
Subject:   change default web server to Apache?
Date:   2002-10-09 14:48:57
From:   anonymous2
Is this possible?


I followed the instructions in the ColdFusion installation manual, and kept getting the error:


web server Apache is not configured for Mac OS X


The instructions say to use the java distribution that comes with Coldfusion, but I used the one installed with OS X


I would really like to use the same web server for PHP/ColdFusion/Whatever development; not have to switch ports. Any help would be appreciated.

Full Threads Oldest First

Showing messages 1 through 2 of 2.

  • change default web server to Apache?
    2002-10-10 06:53:11  dicklacara [View]

    This has been discussed in previous posts.

    No, you can't use Apache (or any other) web server with CFMX on Mac OS X -- only the Default web server installed by CFMX.

    The reason for this is that interfacing CFMX (actually the underlying JRun) with another web server uses a platform-specific C++ connector module.

    There is no connector-module for the Mac.

    The connector is used to efficiently interface a 3rd-party web server, while protecting MacroMedia's intellectual property -- so this capability probably won't be available for the Mac until/if Macromedia releases a Mac CFMX product.

    Sorry, but that's the way it is.

    Dick

    P.S. If you wanted to get creative, you could trap all Apache "page not founds", and write a PHP program that redirects any .cfm page requests to port 8500
    • change default web server to Apache?
      2003-01-03 10:14:06  lanej0 [View]

      One way I've "worked around" this is to use Apache's proxy ability. In essense, you can intercept requests going to a specific address, pass them to a certain port and then pass the reply back. It's a bit of work, just so you don't have to type :8500 at the end of your URL, but it can be done. I guess that if you need to have a sexy URL because you're using CFMX on a production box, this is a good solution.

      The only real side effect I've found is some funny business that takes place with session variables sometimes and also with obtaining the referrer IP (it will always be localhost).

      If you're really interested in this approach, let me know, and I'll post some sample lines from my httpd.conf to get you up and running. I'm checking back here on a fairly regular basis for Part 4... anytime O'Reilly gets around to editing it.