libp2p / libp2p/specs

http: document how to reference http resources

Open
#554 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

use case wanted
Dominant language
No language data
Stars
1.8k
Forks
320
Avg merge
11d 15h
Merged PRs (30d)
1

Description

Paraphrasing @MarcoPolo "HTTP semantics can run on top of any transport. So these need to be able to be defined on top of any multiaddr not just ones that end in /http" (as documented in https://github.com/libp2p/specs/pull/550)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the issue's reference to libp2p/specs pull request 550 and the surrounding HTTP and multiaddr specification text. Clarify how HTTP resources should be referenced over transports whose multiaddr does not end in /http, then document that rule in the relevant specification section.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, networking
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.