Follow ups to GhostCat - AJP connector #1583
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#1533
Checklist
Description of change
2020.1.0 included tomcat 8.5.51 , and subsequently broke the AJP connector.
This PR fixes the AJP connector with the following:
mandatory-config.properties
:ajp.secret.required
- it should be set tofalse
for now. Default istrue
since it's more secureajp.address
- Default is127.0.0.1
Another configuration,
ajp.secret
, was added in, but should be considered a beta feature. The default valueignore
ofajp.secret
will do just that.I am waiting to test
ajp.secret
until httpd 2.4.42+ is released into the repos - currently looks like it doesn't have full approval of the community. It would be appreciated if folks in the community can confirmajp.secret
works with a different web server, and thenajp.secret
can move out of beta.Support for ajp secret in httpd 2.4.42 : https://www.apachelounge.com/viewtopic.php?t=8448
Issues with 2.4.42 / 2.4.43 : https://www.apachelounge.com/viewtopic.php?t=8441