Loading...

This issue is archived. You can view it, but you can't modify it. Learn more

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Major
Component/s: core
Labels:
- issue-exported-to-github

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

Assignee:: Kohsuke Kawaguchi
Reporter:: vjuranek

Created:: 2013-01-15 19:03
Updated:: Yesterday 10:22
Resolved:: 2013-03-01 01:35
Archived:: Yesterday 10:22

Details

Description

Attachments

Issue Links

Activity

People

Dates