/ipfs/ and /ipns/ links don't work from a dnslink hosted web space · ipfs/kubo#3902

(6 评论) (2 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import

help wanted

描述

Version information:

go-ipfs version: 0.4.9-rc1- Repo version: 5 System version: amd64/darwin Golang version: go1.8

Type: Bug

Severity: Medium

Description:

When accessing IPFS via a dnslink-serviced host (e.g. ipfs.sallings.org), /ipfs/ and /ipns/ links don't work.

e.g.,:

http://ipfs.sallings.org/ipns/QmP8uqUuowHdixyFASba87ABgVxfoKGj8NyrTH2VLLTFkZ

yields:

ipfs resolve -r /ipns/ipfs.sallings.org/ipns/QmP8uqUuowHdixyFASba87ABgVxfoKGj8NyrTH2VLLTFkZ: no link named "ipns" under QmaYYjrg1rEYddWYLcR96uc9jGLA9cuHkUiCqQYLwbKDnx

I would expect either ipfs or ipns to be handled in this case when it can't be resolved directly (or just always).

This seems minor, but I considered it "medium" severity as it means you can't link to separately managed pages within IPFS from such a host. In the above case, I worked around this by linking to //gateway.ipfs.io/ipns/... -- but this is quite undesirable for a variety of reasons (e.g., can't just browse stuff at localhost).

贡献者指南

技术栈: go
领域: backend
议题类型: bug
难度: 3
预计时间: 1-3 hours
活动状态: stale
清晰度: clear
前置要求: Basic understanding of IPFS gatewayGo programming
新手友好度: 35
研究方向: Investigate the gateway's handling of /ipfs/ and /ipns/ paths when accessed via a DNS link. Look at the path resolution logic in gateway.go or similar files; the error indicates the gateway is trying to resolve the entire path including the DNS hostname. The fix should ensure that nested /ipfs/ and /ipns/ prefixes are resolved correctly, possibly by stripping the hostname or handling the path segments appropriately. Check existing tests and comments for context.