docs: simplify canister ID resolution and rename API Gateway to API Boundary Node in HTTP GW spec#6230
Merged
r-birkner merged 2 commits intoApr 21, 2026
Conversation
…oundary Node in HTTP GW spec Remove implementation-specific canister ID resolution logic (hostname table, raw domain handling, DNS TXT lookup, x-ic-canister-id header) and replace with a protocol-agnostic description that lists example approaches. Also rename "API Gateway" to "API Boundary Node" throughout.
github-actions
Bot
added
the
interface-spec
viviveevee
approved these changes
Apr 21, 2026
raymondk
approved these changes
Apr 21, 2026
r-birkner
deleted the
rjb/remove-canister-id-resolution-from-http-gw-spec
branch
April 21, 2026 20:22
Contributor
|
I suppose there was a high-level decision to do this, but I still wonder if there are any docs on how the canister ID resolution actually works now? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
x-ic-canister-idheader detection) from the HTTP Gateway Protocol Spec, replacing it with a protocol-agnostic description that lists example approaches (subdomain encoding, DNS, static mapping, HTTP header).