No connection keep-alive
I were investigating why Runner opens new TCP connection every request to GitLab.com.
It appears that the server doesn't send the Connection: keep-alive
in response to client.
As this is something that needs to be send by client,
it appears that this overwritten be workhorse.
Workhorse strips the Connection
header.
Without keep-alive
we force clients to open new connection every request, thus worsening the experience.
@jacobvosmaer Could we verify that this is actually the case?