docs: drop the path-suffixed metadata deviation, now fixed server-side - #1
Merged
Merged
Conversation
usable.dev now serves the RFC 9728 §3.1 path-suffixed protected-resource document at /.well-known/oauth-protected-resource/api/mcp, identical to the origin-level one, and returns JSON 404 rather than the app shell for unmatched paths in that namespace. Clients that construct the metadata URL by convention instead of reading resource_metadata from the WWW-Authenticate challenge now complete discovery, so the deviation notes no longer describe a live defect. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
usable.devnow serves the RFC 9728 §3.1 path-suffixed protected-resource document at/.well-known/oauth-protected-resource/api/mcp, byte-identical to the origin-level one, and returns JSON404rather than the app shell for unmatched paths in that namespace.Clients that construct the metadata URL by convention — instead of reading
resource_metadatafrom theWWW-Authenticatechallenge — now complete discovery, so the deviation notes no longer describe a live defect.docs/authentication.md— "Known deviation" replaced with a short note that either discovery strategy works.docs/supported-clients.md— the ecosystem-deviation entry marked fixed rather than deleted, so the history stays legible.docs/troubleshooting.md— the diagnostic now curls both metadata URLs and expects them to agree.Verify after deploy:
🤖 Generated with Claude Code