ipfs/ipfs-companion

Localhost URLs not redirected

Open

#926 opened on Sep 30, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
P2effort/daysexp/experthelp wantedkind/bug

Description

Describe the bug URLs pointing to localhost don't properly redirect when using an external IPFS node.

To Reproduce

  1. Configure IPFS companion to use an external node (e.g. http://192.168.0.100:5001)
  2. Navigate to http://localhost:8080/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme and note it does NOT redirect.
  3. Navigate to http://gateway.ipfs.io/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme and note that it DOES redirect to your external node.

Expected behavior All URLs get detected and redirected to specified node; when entering http://localhost:8080/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme into the URL bar, it should replace and load CONFIGURED_EXTERNAL_NODE/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme instead.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Brave
  • Version: 1.14

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptbrowser extension conceptsIPFS basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate how the extension detects IPFS gateway URLs and redirects them to the configured external node. Look for logic that processes URL patterns in the background script or content scripts. Check for any special handling of 'localhost' that might skip the redirect. The issue mentions that gateway.ipfs.io works but localhost:8080 does not, so there may be a missing case in URL matching.