-
Bug
-
Resolution: Fixed
-
Major
-
None
Some links (e.g. in console output lnks "Building remotely on slaveXYZ") don't preserve protocol and have hardcoded HTTP even if the page is opened via HTTPS. This can be considered as a security risk (e.g. user doesn't notice change of the protocol and later on can open another console output with sensitive data and the data would be sent over unsecure HTTP in this case)
- is duplicated by
-
JENKINS-16511 Jenkins behind a proxy sends JNLP agents incorrect URL
- Resolved
-
JENKINS-16613 Windows slave fails to start via JNLP (wrong URL scheme + fails to redirect)
- Resolved
-
JENKINS-16626 Remote access API does not deal with a jenkins server only available through https
- Resolved
-
JENKINS-16656 slave agent fails to start: slave-agent.jnlp uses http while jenkins url is https
- Resolved
- is related to
-
JENKINS-16802 Using Apache proxysettings breaks several GUI functions
- Resolved