ipfs/ipfs-companion

Autodetect "Custom Local Gateway" being wrong

Open

#629 opened on Nov 26, 2018

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (364 forks)batch import
good first issuehelp wantedkind/enhancementstatus/ready

Repository metrics

Stars
 (1,992 stars)
PR merge metrics
 (Avg merge 53d 3h) (1 merged PR in 30d)

Description

I am often running other services than IPFS on port 8080, at the moment Syncthing, but I have previously ran HTTP caching proxies and IRC bot web interfaces there. The result is that when I try to access IPFS resource, Syncthing gives me a 404 error and I spend a moment investigating why this happens before remembering that my IPFS is actually on port 8082.

I think more useful behaviour would be IPFS companion attempting to check that http://127.0.0.1:8080/ actualy works and if it returns 404 or something else unexpected, it would prompt me and ask have I configured it correctly.

Contributor guide

Research direction
Examine the current autodetection logic in ipfs companion and add a health check against the configured gateway URL to verify it responds correctly before using it.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80