AJP proxy of request environment

[Cantor, Scott]

On 7/20/12 5:50 PM, "Chad La Joie" <lajoie at itumi.biz> wrote:
>
>None of that really has anything to do with which protocol is used to
>send the data from the webserver to the container, however.

No, but the part you quoted wasn't talking about that piece.

You must have meant the part about AJP bias. The reason there is, AJP is
faster (unless the AJP code sucks), and it isn't vulnerable to URL
rewriting problems. Reverse proxying is just very fragile, though
seemingly less so these days.

The other advantage is mostly security by obscurity. It's easy to
accidentally leave open something being HTTP-proxied, since any browser is
an attack tool. AJP at least is a binary protocol that's not open to a
browser, and because of the ports it uses and such, just isn't as likely
to accidentally get exposed.

-- Scott