Migrating from AJP to HTTP: It's About Time
Channel: The ASF
Date: 2020-10-23

Migrating from AJP to HTTP: It's About Time
Christopher Schultz

A presentation from ApacheCon @Home 2020
https://apachecon.com/acah2020/

The Apache JServ Protocol was developed in 1997 as a proxying protocol between Apache httpd and Apache Jserv. At the time, mod_proxy was not an option for connecting to Apache Jserv, so Apache mod_jk was developed and generations of developers have used it to great effect. But AJP has some serious flaws, including lack of encryption and the inability to upgrade connections to use Websockets. In the intervening years, mod_proxy has become much more fully-featured and can solve all the problems with using AJP. We will cover all of the reasons AJP should be abandoned, all the nice things mod_jk does for you, and how to achieve the same results using mod_proxy with the http and wstunnel child-mods.

Christopher Schultz is the CTO of Total Child Health, Inc. where he leads a small team of engineers to build server-side healthcare-related software in Java. Chris is an ASF Member active in the Apache Tomcat and Velocity communities as well as a committer on both projects, and Tomcat PMC and security team member. He has attended and spoken at several previous ApacheCon events and helped to organize an Apache BarCamp in the Washington, DC area.