--api doesn't handle http/https urls appended to the multiaddr format

[wrouesnel]

Version information:

go-ipfs version: 0.4.3-
Repo version: 4
System version: amd64/linux
Golang version: go1.7

Type:

Enhancement

Priority:

P2

Description:

A fairly logical use-case for the ipfs daemon for a home user is on a network exit point with some persistently attached storage (i.e. a file server). The ipfs client already supports remote API connections with --api, and the multiaddr library supports passing https urls.

However currently the IPFS client ignores additional address path segments passed with --api
i.e. ipfs --api /ip4/192.168.1.10/tcp/443/https/ipfs-node.some-remote-server.local/ id

In both cases "Error: no protocol with name ipfs-node.some-remote-server.local" is generated in response (DNS name changed).

[whyrusleeping]

cc @lgierth

[hoh]

I am facing this issue as well.

Fixing it in the Python aiohttp library is trivial, what prevents its implementation in the official CLI ?

[lidel]

Fixed in master, will be released in 0.33: #9897 (comment)