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

libp2phttp: Rename well-known resource #2757

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Conversation

MarcoPolo
Copy link
Collaborator

Renaming the well-known libp2p http resource. Context here: libp2p/specs#508 (comment)

@MarcoPolo MarcoPolo merged commit 46ef49e into master Apr 15, 2024
11 checks passed
lidel added a commit to ipfs/specs that referenced this pull request Apr 19, 2024
@@ -30,6 +30,7 @@ import (
var log = logging.Logger("libp2phttp")

const ProtocolIDForMultistreamSelect = "/http/1.1"
const WellKnownProtocols = "/.well-known/libp2p/protocols"
Copy link
Contributor

@gammazero gammazero May 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarcoPolo Changing this from "/.well-known/libp2p" to "/.well-known/libp2p/protocols" will break the ability to communicate with existing servers deployed without upgrading them first. Since these servers are running in places not under our control, they will not be immediately upgradable.

This means that libp2phttp needs to support both the old and the new values, or revert to using the old value.

Since there are already deployments using the old value, I suggest changing this to:

const WellKnownProtocols = "/.well-known/libp2p"

gammazero added a commit that referenced this pull request May 16, 2024
Changing from "/.well-known/libp2p" to "/.well-known/libp2p/protocols" will break the ability to communicate with existing servers deployed without upgrading them first. Since these servers are running in places not under our control, they will not be immediately upgradable. This means that libp2phttp needs to support both the old and the new values, or revert to using the old value.

This PR reverts to using the old resource name, which was changed in #2757.
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.

3 participants