This repository has been archived by the owner on Mar 10, 2020. It is now read-only.
Fix support for /https multiaddrs passed to constructor #965
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug
Pointing Web UI at
/https
multiaddr did not work: it was not able to connect to API over HTTPS, always tried HTTP (ipfs/ipfs-webui#989):I tracked the bug up to
ipfs-http-client
constructor: onlyhost
andport
were read from multiaddr,protocol
was ignored and unencrypted HTTP was used for all multiaddrs:https://github.com/ipfs/js-ipfs-http-client/blob/21cdcc5100b32e3ac1e75ec70022b9b28b0aede1/src/index.js#L27-L28
Fix
This PR: