Ajp13

 

Usage

Ajp13

This module is used to reverse proxy to a backend application server (e.g. Apache Tomcat) using the AJP13 protocol. The usage is similar to an HTTP reverse proxy, but uses the ajp:// prefix:

Nov 05, 2014 In addition, the ARR module does not require any additional configuration on the Tomcat side, (including opening the 8009 AJP13 redirect port). The configuration for ARR can be extended to support a multitude of load balancing configurations and can be configured to redirect to any number of Web Application servers (not just Tomcat!). Important changes. HTTP /2 enabled by default, moddeflate zstd support, modajp13 (new), bugfixes. Lighttpd-1.4.59.tar.gz (GPG signature). Encapsulated AJP13 traffic when using NAT. Security Server: ESP: Connection Server: Encapsulated AJP13 traffic when NAT traversal is not required. ESP is IP protocol 50. Port numbers are not specified. Security Server: AJP13: Connection Server: TCP 8009: AJP13 traffic without IPsec and during pairing. Security Server: JMS: Connection. Important changes. HTTP /2 enabled by default, moddeflate zstd support, modajp13 (new), bugfixes. Lighttpd-1.4.59.tar.gz (GPG signature).

Options such as the secret option of Tomcat (required by default since Tomcat 8.5.51 and 9.0.31) can just be added as a separate parameter at the end of ProxyPass or BalancerMember. This parameter is available in Apache HTTP Server 2.4.42 and later:

Simple Reverse Proxy with secret option

Balancers may also be used:

Note that usually no ProxyPassReverse directive is necessary. The AJP request includes the original host header given to the proxy, and the application server can be expected to generate self-referential headers relative to this host, so no rewriting is necessary.

What Is Ajp13

The main exception is when the URL path on the proxy differs from that on the backend. In this case, a redirect header can be rewritten relative to the original host URL (not the backend ajp:// URL), for example:

Ajp13port

Ajp13

Ajp13 Error

Rewriting Proxied Path

Port 8009

However, it is usually better to deploy the application on the backend server at the same path as the proxy rather than to take this approach.