-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Labels
kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featureneed/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritizationtopic/gatewayTopic gatewayTopic gateway
Description
If you make a {cidv0}.ipfs.dweb.link subdomain URL with a v0 CID, you get:
invalid ipfs path: invalid path "/ipfs/{cidv0}/": invalid CID: selected encoding not supported
Browsers force-lowercase authority part of every URI which breaks CIDv0.
That is why advise use of dweb.link/ipfs/{cidv0} as canonical link (it coverts and redirects, working around browser limitations).
Perhaps we could special-case this natively in go-ipfs, and detect that error was caused by "broken cidv0" starting with qm.. ?
That is what we already do in ipfs-companion in Firefox: ipfs/ipfs-companion#911:
At very minimum we could make text error more useful by detecting qm.. and providing more useful error suggesting to "covert CIDv0 to CIDv1 in base32 and try again"?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featureneed/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritizationtopic/gatewayTopic gatewayTopic gateway
