-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal - Deprecate AJP support #10098
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I agree to remove the feature from ajp. I don't see many users in the community using it and keeping unused functionality is not worth keeping in the project. |
Used a lot in the past, with Tomcat backends, but no more actually used on Kubernetes. |
Hello, Given your arguments and the general concern over the C library, it is more then reasonable to remove it IMHO. |
As I wrote in the comment, we used a fork version of the AJP module because the original module has not yet added support for NGINX v1.21 and the project is inactive. yaoweibin/nginx_ajp_module#52 ingress-nginx/images/nginx/rootfs/build.sh Lines 83 to 86 in b47409a
I'm +1 for removing this feature. |
+1 |
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!
The text was updated successfully, but these errors were encountered: