On Fri, 11 Apr 2008, Bart Whiteley wrote:

> In order to add this enhancement to libcurl, we need to determine how to
> encode the path to the unix socket in an HTTP URL. Or, if this doesn't seem
> feasible, we need some other way to tell libcurl the path to the unix
> socket. I have been unable to find a standard or convention for encoding a
> unix socket path in an HTTP URL.

Generic URIs are defined in RFC3986 but that one doesn't explictly define
HTTP. RFC1738 was at least explict about HTTP and it says "host" and leaves no
room for an domain path in there to remain a valid HTTP URL.

I noticed that the OpenLDAP people introduced a ldapi:// for exactly this
purpose (providing a path instead of a host name/address). But then I don't
think LDAP has this vhost problem I mentioned...

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html