When using unix socket, there were 2 problems with the old implementation:
host header was set with the value :0, which is invalid
the path to the unix socket was used as path in HTTP POST
Proposed fix included in this pull request
set Host header to the empty value (a valid value and recommended situations without hostname)
use / path in http request since it is the only reasonable as there's no way to specify the http path in the configuration (the unix:// scheme doesn't have any way to specify it, it defines a path to the socket)
When using unix socket, there were 2 problems with the old implementation:
:0, which is invalidProposed fix included in this pull request
/path in http request since it is the only reasonable as there's no way to specify the http path in the configuration (theunix://scheme doesn't have any way to specify it, it defines a path to the socket)