custom IPFS API URL is not supported - ipfs companion doesn't support subpaths for custom API

ipfs / ipfs-companion

Browser extension that simplifies access to IPFS resources on the web

https://docs.ipfs.tech/install/ipfs-companion/

Creative Commons Zero v1.0 Universal

2.05k stars 325 forks source link

custom IPFS API URL is not supported - ipfs companion doesn't support subpaths for custom API #1043

Open master-hax opened 2 years ago

master-hax commented 2 years ago

Describe the bug my custom API URL http://localhost/ipfs-api works well from the IPFS web UI, however this browser companion gives me an error when i enter the custom HTTP path

To Reproduce Steps to reproduce the behavior:

Go to extension settings
Edit IPFS API URL to have a path in it
See error

Expected behavior I expect the custom path to work like it does in the IPFS web UI (CID bafybeif4zkmu7qdhkpf3pnhwxipylqleof7rl6ojbe7mq3fzogz6m4xk3i)

Screenshots (sorry for the weird screenshot i think it is an HDR issue)

Desktop (please complete the following information):

OS: Windows
Browser: Opera
Version: 82.0.4227.43

welcome[bot] commented 2 years ago

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 commented 2 years ago

@master-hax Thanks for your contribution. Unfortunately, we don't have the bandwidth to take this on at the moment, but if you change your custom API to not have a subpath, it should work.

You can edit your hosts file and use something like http://ipfs-api.localhost to get around this lack of functionality for now.

master-hax commented 2 years ago

hi @SgtPooki appreciate the response. i think leaving this issue open may be useful for others who come across the same discrepancy in API usage across official IPFS projects.