-
Bug
-
Resolution: Fixed
-
Major
broken HTTP_PROXY handling on jenkins-slave (JNLP)
The proxy exclusion list (http.nonProxyHosts, no_proxy) is not taken into account on the jenkins-slave side.
This has been observed in our jenkins master/slave environment which uses JNLP.
Support for HTTP_PROXY handling on jenkins-slave side has been added with jenkins version 1.606.
Unfortunately that does not take the proxy exclusion list into account (e.g. defined by no_proxy env variable on linux).
This forces the slave to always use the proxy. Even for destinations which would be excluded by no_proxy.
Jenkins uses org.jenkins-ci.main:remoting for handling http proxy functionality.
Jenkins includes version 2.53.2 of org.jenkins-ci.main:remoting which contains the error described above.
possible solution:
1.) create new release of org.jenkins-ci.main:remoting which already contains the fix in it's master branch.
2.) update jenkins' to use this new version of org.jenkins-ci.main:remoting
see also:
- commit of fix in master branch of org.jenkins-ci.main:remoting
https://github.com/jenkinsci/remoting/commit/56d30acb89f5626320d6b47585053674a5fdfb78
- is related to
-
JENKINS-48778 JNLP not considering plain hostnames when evaluating NO_PROXY
-
- Resolved
-
- links to
[JENKINS-32326] broken HTTP_PROXY handling on jenkins-slave (JNLP)
Description |
Original:
*broken HTTP_PROXY handling on jenkins-slave (JNLP)* The proxy exclusion list (http.nonProxyHosts, no_proxy) is not taken into account on the jenkins-slave side. This has been observed in our jenkins master/slave environment which uses JNLP. Support for HTTP_PROXY handling on jenkins-slave side has been added with jenkins version 1.606. Unfortunately that does not take the proxy exclusion list into account (e.g. defined by no_proxy env variable on linux). This forces the slave to always use the proxy. Even for destinations which would be excluded by no_proxy. Jenkins uses [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] for handling http proxy functionality. Jenkins includes version 2.53.2 of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] which contains the error described above. possible solution: 1.) create new release of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] which *already *contains the fix in it's master branch. 2.) update jenkins' to use this new version of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] see also: - commit of fix in master branch of org.jenkins-ci.main:remoting [https://github.com/jenkinsci/remoting/commit/56d30acb89f5626320d6b47585053674a5fdfb78] |
New:
*broken HTTP_PROXY handling on jenkins-slave (JNLP)* The proxy exclusion list (http.nonProxyHosts, no_proxy) is not taken into account on the jenkins-slave side. This has been observed in our jenkins master/slave environment which uses JNLP. Support for HTTP_PROXY handling on jenkins-slave side has been added with jenkins version 1.606. Unfortunately that does not take the proxy exclusion list into account (e.g. defined by no_proxy env variable on linux). This forces the slave to always use the proxy. Even for destinations which would be excluded by no_proxy. Jenkins uses [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] for handling http proxy functionality. Jenkins includes version 2.53.2 of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] which contains the error described above. possible solution: 1.) create new release of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] which *already* contains the fix in it's master branch. 2.) update jenkins' to use this new version of [org.jenkins-ci.main:remoting|https://github.com/jenkinsci/remoting] see also: - commit of fix in master branch of org.jenkins-ci.main:remoting [https://github.com/jenkinsci/remoting/commit/56d30acb89f5626320d6b47585053674a5fdfb78] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Remote Link | New: This issue links to "PR#84 (Web Link)" [ 14348 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Etienne Bec [ etiennebec ] |
Assignee | Original: Etienne Bec [ etiennebec ] | New: Oleg Nenashev [ oleg_nenashev ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | New: lts-candidate |
Labels | Original: lts-candidate | New: 2.7.2-fixed lts-candidate |
Labels | Original: 2.7.2-fixed lts-candidate | New: 2.7.2-fixed |