Because there are multiple protocols you could be using to talk to the socket other than HTTP. In order to use HTTP, you also need to specify the path and maybe other elements. What you may want is something like:
http://<unix:///tmp/my.sock>/foo/bar.html?good=yes
To avoid the nesting of protocols, I think it is cleaner to give it a name and define the socket path elsewhere.
