IPFS API URL with user information is not supported.

[vbalien]

Describe the bug It will not work if the IPFS API URL contains user information.

To Reproduce Steps to reproduce the behavior:

1. I tried setting my IPFS API URL to https://user:[email protected]
2. But it doesn't work.

Expected behavior It should work even if the IPFS API URL contains user information.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within seven business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[SgtPooki]

@vbalien Hey there, the go implementation of IPFS does not implement basic auth, so this feature cannot be easily added in the companion extension. We will have to backlog this until someone is able to add basic-auth to the go implementation of IPFS.