"Jenkins URL" setting in configure page plays multiple role in Jenkins. Seems it is not as simple as extract it from E-mail configuration section (JENKINS-1669).

We hosted our Jenkins (http://10.144.37.34:8082/jenkins) behind Apache2 HTTP server with reverse proxy (http://10.144.113.114/jenkins).

Once we set the "Jenkins URL" to the URL of the Apache server, our JNLP slave agent connect to the wrong URL (10.144.113.114:random_jnlp_port instead of 10.144.37.34:random_jnlp_port).

If we left the "Jenkins URL" field blank intentionally (JENKINS-3873). In addition to the e-mail notification with wrong URL, Jenkins always guesses URL from HTTP request and populates it into the "Jenkins URL" field in configuration page. Once we submit the page without modify it to blank manually, JNLP slave agent failed to connect server next time, again and again...

Is it okay to separate the Jenkins URL into something like "Public Jenkins URL" and "Private Jenkins URL",
or current "Jenkins URL" with advance option to set the "Jenkins Server URL"?