when will ColdFusion 10 (or higher) support apache 2.4?

I had to change a few things in the mod_jk.c source file, but I got it to compile, and it seems to be working just fine with apache 2.4 on ubuntu 13.10.  This is totally unsupported at this point, of course, but I've had no problems with it on my dev server in the brief time I've tested it.  The changes were relatively minor, and on my ubuntu 13.10 dev server, the result is a working connector.

Here are the steps:

• install apache2-dev or its equivalent (for ubuntu: "sudo apt-get install apache2-dev").

• download source for mod_jk: https://helpx.adobe.com/coldfusion/kb/rhel-connector-configuration/_jcr_content/main-pars/download_1/file.res/connector-source.zip

• unzip the archive somewhere where you can work on it.

• go into the native folder:

  cd ./connector-source/native
  

• change the "configure" script so it is executable:

  chmod 775 configure
  

• figure out where your system's apxs (an apache program) is:

  which apxs
  

• This should result in a full path to the apxs command.  If not, this used to be a sign that you had apache's threaded version installed instead of the prefork mtm.  Used to be you'd install package "apache2-prefork-dev" to fix this (see http://ubuntuforums.org/showthread.php?t=1425646).  Not sure how this would work in 13.10 with 2.4, but I didn't run into this problem.

• using the path to the apxs executable from the "which" command, run the following command:

  ./configure --with-apxs=<apxs_path>
  

  so, for ubuntu 13.10, for example, the apxs path is /usr/bin/apxs:

  ./configure --with-apxs=/usr/bin/apxs
  

• now, we fix problems with connector for apache 2.4:

  • in mod_jk.c (connector-source/native/apache-2.0/mod_jk.c):

    • replace all mentions of "r->connection->remote_ip" with "r->connection->client_ip" (lines 832 and 1106).

    • replace all mentions of "r->connection->remote_addr" with "r->connection->client_addr" (line 833).

    • use the following pattern to fix calls to ap_log_error (from http://httpd.apache.org/docs/current/developer/new_api_2_4.html):

      /* code for httpd 2.0/2.2 */
      ap_log_perror(file, line, APLOG_ERR, 0, p, "Failed to allocate dynamic lock structure");
      
      /* code for httpd 2.4 */
      ap_log_perror(file, line, APLOG_MODULE_INDEX, APLOG_ERR, 0, p, "Failed to allocate dynamic lock structure");
      

    • in the actual file, the lines changed (735 and 741) looked like:

      // before
      ap_log_error(file, line, APLOG_MODULE_INDEX, level, 0, s, res);
      
      // after
      ap_log_error(file, line, APLOG_MODULE_INDEX, APLOG_ERR, level, 0, s, res);
      

• update the actual build script so it is executable:

  chmod 775 ./scripts/build/instdso.sh
  

• run make to build the connector:

  make

• if no errors, newly compiled mod_jk.so should now be in connector-source/native/apache-2.0/ --> connector-source/native/apache-2.0/mod_jk.so

• move existing mod_jk.so out of the way.  In new terminal:

  cd <path_to_CF10_install>/config/wsconfig/<magic_number>
  (sudo) mv mod_jk.so mod_jk.so.orig.bak
  

  In ubuntu 13.10:

  • path_to_CF10_install = /opt/coldfusion10
  • magic_number for me has always been 1, but you might have to just go to the config/wsconfig and see what is there.

• copy newly compiled version of mod_jk.so into place:

  cp <path_to_connector-source>/native/apache-2.0/mod_jk.so <path_to_CF10_install>/config/wsconfig/<magic_number>/
  

  so, if you are in the native directory, for a standard ubuntu install:

  (sudo) cp ./apache-2.0/mod_jk.so /opt/coldfusion10/config/wsconfig/1/
  

• restart apache and ColdFusion, then test.

In addition, you will need to update your site configuration when migrating from 2.2 to 2.4 (httpd.apache.org/docs/2.4/upgrading.html).

The things that got me that I made a note of:

• change all instances of:

  Order allow,deny
  
  Allow from all
  

  to:

  Require all granted
  

• change all instances of:

  Order deny,allow
  
  Deny from all
  
  Allow from 127.0.0.0/255.0.0.0 ::1/128
  

  to:

  Require host 127.0.0.0/255.0.0.0 ::1/128
  

• And, apache 2.4 on ubuntu changes the naming conventions of things in /etc/apache2/sites-available - they all now have to end in ".conf".  So, if you have any custom sites in sites-available, you'll need to add ".conf" to the end of the file names there.