-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Add support to configure AJP as the only enabled connector #85
Milestone
Comments
how so? |
|
okay. would you like to submit a patch? |
Assuming I would remove the connector. The custom fact which is revealing the current JIRA version would then have to talk to the Apache sitting in front of JIRA. Do you think adding support for HTTPS is the only thing that's missing (besides dealing with self-signed certificates)? Or are there other things that could break? |
oranenj
added a commit
to oranenj/puppet-jira
that referenced
this issue
Apr 19, 2021
cegeka-jenkins
pushed a commit
to cegeka/puppet-jira
that referenced
this issue
Oct 13, 2021
…e default HTTP connector (voxpupuli#369) * Allow disabling the default connector. Fixes voxpupuli#85 * Bump MySQL connector version to something non-EOL. Still works with older mysql
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running JIRA behind an Apache reverse proxy enables the usage of AJP to do all communication via the AJP rather than HTTP. Unfortunately, the module still requires to configure the regular tomcat HTTP connector.
Being able to disable the HTTP connector and only use the AJP one would make the configuration a bit cleaner.
The text was updated successfully, but these errors were encountered: