mod_proxy_ajp 或 mod_jk 应该用于生产环境吗？
这几天我一直在寻找是否应该使用mod_proxy_ajp或mod_jk来连接apache httpd和tomcat。我找到的所有网站都有几年历史并且已经过时了。
那么，哪个最适合用于适当的生产环境呢？ mod_proxy_ajp 是否足够成熟以完全取代 mod_jk，或者如果您可以正确配置它，mod_jk 仍然是最好的吗？另外，配置每个连接器时的难度有何差异？
I've been searching over the past few days of whether I should use mod_proxy_ajp or mod_jk to connect apache httpd and tomcat. All the sites I find are a few years old and outdated.
So, which is best to use for a proper production environment? Is mod_proxy_ajp mature enough to entirely replace mod_jk, or is mod_jk still best if you can configure it correctly? Also, what's the difference in difficulty when configuring each connector?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我已经在生产环境中使用 mod_jk 大约 4 年了。它做了它应该做的事，我不需要考虑它。我没有理由改变它。
对于新服务器，我会坚持使用我已经知道的有效方法，除非有令人信服的理由不这样做。
功能并不完全重叠。我还记得在某处读到 mod_jk 更快。
I've had mod_jk in production for about 4 years. It does what it's supposed to, and I don't have to think about it. I have no reason to change it.
For a new server I'd stick to what I already know works, unless there was a compelling reason not to.
The functionality isn't a complete overlap. I also remember reading somewhere that mod_jk is faster.