Skip to content

Proposal - Deprecate AJP supportΒ #10098

@rikatz

Description

@rikatz

AJP has been on Ingress NGINX since 2018. For those who don't know it, it is a binary protocol usually used to communicate with Java backends (Tomcat, Jboss, etc).

The fact is that while AJP is really useful on some specific scenarios (binary communications, huge headers, etc) it is not a really used feature (I couldn't see people doing comments on it while using ingress).

To use AJP we have a dependency on a module that is written in C, not updated since 2021. It is a security concern for the project. Also, usually the Java backends that rely on AJP can also use HTTP without any big issues, unless you really need some specific AJP feature.

My proposal is to remove the AJP support on the next minor release (1.9) and reduce our compilation scope, the amount of annotation and codes, etc.

Please add a +1 or -1 but also leave your comment on why!

Thanks!

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions