Repository navigation
[JENKINS-6167] JNLP slave should support a connection via HTTP proxy #19480
Description
It's possible to use the standard HTTP proxy to bridge arbitrary TCP/IP connection — the CONNECT command.
JNLP slaves should support this.
Originally reported by 
kohsuke, imported from: JNLP slave should support a connection via HTTP proxy
- assignee:
shirosaki
- status: In Progress
- priority: Major
- component(s): core
- resolution: Unresolved
- votes: 2
- watchers: 5
- imported: 2025-11-24
Raw content of original issue
It's possible to use the standard HTTP proxy to bridge arbitrary TCP/IP connection — the CONNECT command.
JNLP slaves should support this.
Activity
jenkins-infra-bot commentedon Aug 4, 2010
Raw content of original comment:
This patch shows how to do it by hard coding my proxy settings... hopefully this solves half the problem (the other half being how to not hard code my settings)
jenkins-infra-bot commentedon Oct 2, 2012
Raw content of original comment:
Slave behind http proxy works with this patch.
Use http_proxy environment variable.
jenkins-infra-bot commentedon Oct 17, 2014
Raw content of original comment:
shirosaki: Please submit patches as pull requests on GitHub.
jenkins-infra-bot commentedon Oct 18, 2014
Raw content of original comment:
I've submitted a patch on GitHub.
jenkinsci/remoting#27
jenkins-infra-bot commentedon Mar 20, 2015
Raw content of original comment:
Code changed in jenkins
User: Hiroshi Shirosaki
Path:
src/main/java/hudson/remoting/Engine.java
src/main/java/hudson/remoting/Launcher.java
src/main/java/hudson/remoting/Util.java
http://jenkins-ci.org/commit/remoting/8c875cbc81d22df898a57ef86e833b41c50470cb
Log:
JENKINS-6167 Support JNLP slave connection via HTTP proxy
We get proxy setting from http.proxyHost property or http_proxy
environment variable.
jenkins-infra-bot commentedon Mar 20, 2015
Raw content of original comment:
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
pom.xml
http://jenkins-ci.org/commit/jenkins/72e0b9c53a15306e0a7b7117100f4d1b7ec250b8
Log:
[FIXED JENKINS-6167 JENKINS-21251 JENKINS-21160]
Integrated a newer version of remoting & args4j
jenkins-infra-bot commentedon Mar 27, 2015
Raw content of original comment:
JENKINS-21618JENKINS-22941JENKINS-25938JENKINS-26391JENKINS-26900JENKINS-27476JENKINS-27563JENKINS-27564JENKINS-27565JENKINS-27566Code changed in jenkins
User: Stephen Connolly
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/46dc6850edb1d7ef52592794b15e69db7dfbed1a
Log:
Noting merges
JENKINS-21618JENKINS-22941JENKINS-25938JENKINS-26391JENKINS-26900JENKINS-27476JENKINS-27563JENKINS-27564JENKINS-27565JENKINS-27566jenkins-infra-bot commentedon Jun 9, 2016
Raw content of original comment:
JENKINS-31256Use credentials in waitForServerToBack This address three regressions introduced with HUDSON-4071, 662b0f and JENKINS-6167 as these only modified run() resulting in no proxy and no authorization support in waitForServerToBack()Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/hudson/remoting/Engine.java
src/main/java/hudson/remoting/Util.java
http://jenkins-ci.org/commit/remoting/fbb9aff7cf0f9acbba6e97c923efd640b5537c90
Log:
JENKINS-31256Use credentials in waitForServerToBack (#87)JENKINS-31256Use credentials in waitForServerToBackThis address three regressions introduced with HUDSON-4071, 662b0f and JENKINS-6167 as these only modified run() resulting in no proxy and no authorization support in waitForServerToBack()