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.
|Assignee||Oleg Nenashev [ oleg_nenashev ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Remote Link||This issue links to "remoting/pull/146 (Web Link)" [ 15380 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|