ipfs/specs

Manifest files for unixfs loaded via HTTP Gateway

Open

#257 opened on Nov 18, 2021

View on GitHub
 (8 comments) (11 reactions) (1 assignee)HTML (256 forks)batch import
dif/experthelp wantedkind/discussionkind/enhancementkind/maintenanceneed/community-input

Repository metrics

Stars
 (1,108 stars)
PR merge metrics
 (Avg merge 55d 8h) (2 merged PRs in 30d)

Description

This is a placeholder issue for creating a spec for "content root's manifest files" which would be part of the data published on IPFS (eg. /ipfs/CID/_something or /ipfs/CID/.well-known/ipfs/foo) that provides hints to HTTP Gateway around things like redirects, content types and custom HTTP headers.

Related reading:

Possible reuse of:

Feel free to discuss/post ideas below, or open PRs with IPIP drafts that could be reviewed independently.

Contributor guide

Research direction
Study existing specifications and prior art (Netlify, Cloudflare, IPFS redirects) to draft an IPIP for the headers manifest file.
Tech stack
None
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
IPFSHTTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60