-
Bug
-
Resolution: Duplicate
-
Minor
When you setup slave with slave-agent.jnlp it tries to connect to /tcpSlaveAgentListener/ and get JNLP port. I'm not sure if this code is relevant but the check seem to be working like this:
However according to RFC 7230 and RFC 7540 HTTP headers are case-insensitive.
The problem is that if you use proxy written in go agent won't connect with an "java.io.IOException: https://myjenkins.net/ is not Jenkins" error.
See https://github.com/golang/go/issues/21868 for more details.
- duplicates
-
JENKINS-40710 Remoting plugin searches for case-sensitive headers
-
- Resolved
-
[JENKINS-46864] Jenkins agent header check doesn't meet RFC, it's case-sensitive
Summary | Original: Jenkins agent header check is case-sensitive | New: Jenkins agent header check doesn't meet TFC is case-sensitive |
Summary | Original: Jenkins agent header check doesn't meet TFC is case-sensitive | New: Jenkins agent header check doesn't meet RFC, it's case-sensitive |
Component/s | New: remoting [ 15489 ] | |
Component/s | Original: slave-setup-plugin [ 15929 ] |
Labels | New: newbie-friendly |
Assignee | Original: Giuseppe Landolfi [ peppe ] |
Assignee | New: Long Nguyen [ vulong237 ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |