|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Another use case: clustered Tomcat instances behind IIS, url becomes https://%IIS-host%/manager-A, https://%IIS-host%/manager-B, https://%IIS-host%/manager-C, etc. Without leaving an http port open directly to Tomcat, the plugin is unable to reach any specific instance using the currently static "https://%IIS-host%/manager/" URL. If the plugin allows a custom manager URL, any of the instances could be utilized, as well as allow the manager app to be renamed (as described by Beutel).