-
Improvement
-
Resolution: Fixed
-
Minor
-
remoting-2.60+
At my company we have a customer, on whose instance the HTTP proxy replaces the value of the "X-Jenkins-Agent-Protocols" header by the empty string. In such case Remoting 2.60+ is unable to connect, because none of protocols gets accepted.
I would like to add a new system property, which allows disabling the cache on supported protocols. It is not a problem solution, but it should be a good workaround in some cases. It would be also useful to improve diagnostics of such cases.
- links to
Code changed in jenkins
User: Oleg Nenashev
Path:
docs/configuration.md
src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java
http://jenkins-ci.org/commit/remoting/612cc27a3294d11ea13844d972fb44de757864c4
Log:
JENKINS-41730- Add option to ignore the X-Jenkins-Agent-Protocols header (#146)JENKINS-41730- Add option to ignore the X-Jenkins-Agent-Protocols header + improve diagnosticsJENKINS-41730- Switch to org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.protocolNamesToTry according to the feedback from @stephencJENKINS-41730- Pront the list of supported protocols iff it is not emptyJENKINS-41730- Get rid of unnecessary line breaks