Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libp2p + HTTP #1874

Closed
wants to merge 1 commit into from
Closed

libp2p + HTTP #1874

wants to merge 1 commit into from

Conversation

MarcoPolo
Copy link
Collaborator

@MarcoPolo MarcoPolo commented Nov 11, 2022

A draft PR that adds first class support for HTTP as a protocol in libp2p. This came out of various discussions around IPFS camp and 1:1 discussions.

This means:

  • You can write a protocol using HTTP
  • You can use HTTP over libp2p streams.
  • You can use your HTTP protocol over a standard TCP + TLS HTTP connection (even curl works to communicate with a libp2p node, i.e. this works: curl --insecure --cert ./client.cert --key ./client.key https://127.0.0.1:9561/echo -d "Hello World").
  • This enables you to communicate with a peer over standard TCP + TLS HTTP, even if that peer is a dumb static server.

More details in the draft spec:


Note: this is not in the roadmap. This came from seeing the desire when talking to various users around IPFS camp. This work for now will be prioritized below other items in the roadmap unless we agree otherwise.


Do not merge this PR until:

  • We discuss this in the libp2p spec
  • Agree on a protocol ID
  • Agree on the API shown off here
  • Clean up the code. There are various TODOs left since the first pass here is a PoC.

@marten-seemann
Copy link
Contributor

Closing since libp2p now has HTTP support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants