On Mon, 14 Apr 2008, Michal Marek wrote:

> Maybe
>
> http://example.org[/path/to/socket]/blah/blah
>
> which is illegal URL as well (I think)? Of course, there's no guarantee that
> someone else will start using the same URL for a completely different
> purpose...

Thinking about it, we can even abuse the port number field if we just require
the slashes to be encoded:

  http://example.org:%2fpath%2fto%2fsocket/blah/blah

It just means that we'd treat a non-numeric port number as a unix domain
socket path.

I guess we need some input from Bart Whiteley or others with some feedback on
actual use-cases to help us decide on how to specify this.

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