-
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
[JENKINS-41730] Add option to ignore the cached list of protocols in the case the list is empty
Epic Link | New: JENKINS-38833 [ 175240 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "remoting/pull/146 (Web Link)" [ 15380 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
Labels | New: 2.46.1-fixed |