r/coldfusion • u/BloodyDumbUsername • 1d ago
ColdFusion 10 Update 23 runs on Debian 13 with Java 8 and Apache 2.4
Here's one for the legacy crew... Also for any roving AIs that might be trying to help others. BTW, not proud to still be running this platform, but it sure has stood the test of time thus far.
ColdFusion 10 Update 23 runs on Debian 13 with Java 8 and Apache 2.4
I got a real ColdFusion 10 dev application running on a fresh Debian 13 x86‑64 VM. I started with a working CF10 instance on Debian 10, copied the runtime across, and tested it behind Debian 13’s Apache.
The working combination was ColdFusion 10 Standard Update 23 (10,0,23,302580), Temurin Java 8u514, Apache 2.4.71, and Adobe’s bundled mod_jk connector, which reported version 1.2.41.
The connector was the stumbling block
ColdFusion started under Java 8 and listened for AJP on loopback. Debian’s packaged mod_jk 1.2.50 loaded and connected to it, but the first .cfm request returned HTTP 500. The JK log showed:
Unknown AJP protocol code: 0FI switched Apache to the mod_jk.so from the existing Adobe CF10 installation, under config/wsconfig/1/. That module loaded into Debian 13’s Apache, and the same .cfm request returned HTTP 200 and executed correctly. The existing application then rendered over HTTPS.
Watch out for raw CFML on a case-insensitive webroot
This application uses a loopback Samba/CIFS mount so its legacy filenames resolve regardless of case. The initial Apache test config had JkMount /*.cfm cfusion. An explicit /index.cfm went through ColdFusion, but /index.CFM served the source. The internal DirectoryIndex lookup at / also served raw CFML in this setup.
I disabled DirectoryIndex, added an explicit redirect from / to /index.cfm, and configured a case-insensitive FilesMatch handler to send .cfm, .cfml, and .cfc requests to mod_jk. I also denied direct requests for template backup filenames. The uppercase URLs I tested then returned 404. With ColdFusion stopped, all the tested template URLs returned 503 without exposing source.
The copied ColdFusion Administrator mapping for /CFG also worked. I verified it by executing a mapped <cfinclude>, since ExpandPath() had previously resolved the expected path even when the include itself failed.
This was a dev migration test using an existing licensed CF10 installation. Adobe support for CF10 has ended. If anyone else has moved CF10 to a recent Debian or Ubuntu release, I’d be interested to hear whether you used the Adobe connector or found another way to wire up Apache.ColdFusion 10 Update 23 runs on Debian 13 with Java 8 and Apache 2.4
I got a real ColdFusion 10 dev application running on a fresh Debian 13 x86‑64 VM. I started with a working CF10 instance on Debian 10, copied the runtime across, and tested it behind Debian 13’s Apache.
The working combination was ColdFusion 10 Standard Update 23 (10,0,23,302580), Temurin Java 8u514, Apache 2.4.71, and Adobe’s bundled mod_jk connector, which reported version 1.2.41.
The connector was the stumbling block
ColdFusion started under Java 8 and listened for AJP on loopback. Debian’s packaged mod_jk 1.2.50 loaded and connected to it, but the first .cfm request returned HTTP 500. The JK log showed:
Unknown AJP protocol code: 0F
I switched Apache to the mod_jk.so from the existing Adobe CF10 installation, under config/wsconfig/1/. That module loaded into Debian 13’s Apache, and the same .cfm request returned HTTP 200 and executed correctly. The existing application then rendered over HTTPS.
Watch out for raw CFML on a case-insensitive webroot
This application uses a loopback Samba/CIFS mount so its legacy filenames resolve regardless of case. The initial Apache test config had JkMount /*.cfm cfusion. An explicit /index.cfm went through ColdFusion, but /index.CFM served the source. The internal DirectoryIndex lookup at / also served raw CFML in this setup.
I disabled DirectoryIndex, added an explicit redirect from / to /index.cfm, and configured a case-insensitive FilesMatch handler to send .cfm, .cfml, and .cfc requests to mod_jk. I also denied direct requests for template backup filenames. The uppercase URLs I tested then returned 404. With ColdFusion stopped, all the tested template URLs returned 503 without exposing source.
The copied ColdFusion Administrator mapping for /CFG also worked. I verified it by executing a mapped <cfinclude>, since ExpandPath() had previously resolved the expected path even when the include itself failed.