mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 20:37:12 +01:00
c1cd3e85a7
This PR fixes #7062 For hijacked connections, one has to read from the connection buffer, but still write directly to the connection. Otherwise, when reading directly from such connections, the first byte may be lost. This, in turn corrupts the ClientHello TLS handshake message and when the backend server receives it, it closes the connection and reports the following error in the log: ``` http: TLS handshake error from 127.0.0.1:33150: tls: first record does not look like a TLS handshake ``` The first byte may be lost because underlying HTTP request handler may read it from the connection and put it into the buffer. As the result, subsequent connection reads won't see that byte. - See: https://github.com/golang/go/issues/27408 - The fix is taken from : https://github.com/k3s-io/k3s/pull/6216 ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: Artem Fetishev <rtm@victoriametrics.com> |
||
|---|---|---|
| .. | ||
| discovery | ||
| discoveryutils | ||
| testdata | ||
| client_test.go | ||
| client.go | ||
| config_test.go | ||
| config_timing_test.go | ||
| config.go | ||
| relabel_debug.go | ||
| scraper.go | ||
| scrapework_test.go | ||
| scrapework_timing_test.go | ||
| scrapework.go | ||
| targetstatus.go | ||
| targetstatus.qtpl | ||
| targetstatus.qtpl.go | ||