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.

Sign up for GitHub

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

Jump to bottom

Multiaddr URI scheme #165

Open
MarcoPolo opened this issue Aug 25, 2023 · 1 comment · May be fixed by #171
Open

Multiaddr URI scheme #165

MarcoPolo opened this issue Aug 25, 2023 · 1 comment · May be fixed by #171

Comments

@MarcoPolo
Copy link
Contributor

I'd like to propose the following URI scheme for multiaddrs: multiaddr:<string-encoded-multiaddr>.

This would give us the ability to pass in a multiaddr where a URI is expected (e.g. HTTP redirects). A bit more context here: libp2p/specs#568.

I don't think any multiaddrs in use today are incompatible with the generic URI syntax. Specifically section 3.3 for Paths.
@MarcoPolo
Copy link
Contributor Author

For multiaddr components that use multibase, the generator of the URI string should ensure the multibase used is valid as a path segment.

@MarcoPolo MarcoPolo linked a pull request Jun 5, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

URI encoding multiformats/multiaddr
1 participant
@MarcoPolo