Repository navigation
[Doc] State the HTTP status of a require_scopes! failure on the modern path - #597
Merged
koic merged 1 commit intoOct 13, 2026
Conversation
…ern path ## Motivation and Context The Authorization page said that a `require_scopes!` failure inside a handler leaves the HTTP status at 200. That holds on the legacy path and on a modern response streamed as SSE, but a modern response returned as JSON carries the status the transport gives every `-32600`, which is 400. The prose and the Response Reference row now say so. ## How Has This Been Tested? Documentation only. The mapping is `StreamableHTTPTransport#modern_http_status`, which answers 400 for the codes in `MODERN_BAD_REQUEST_CODES`, `-32600` among them, and the existing transport tests cover it. ## Breaking Changes None.
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
1 participant
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.
Motivation and Context
The Authorization page said that a
require_scopes!failure inside a handler leaves the HTTP status at 200. That holds on the legacy path and on a modern response streamed as SSE, but a modern response returned as JSON carries the status the transport gives every-32600, which is 400. The prose and the Response Reference row now say so.How Has This Been Tested?
Documentation only. The mapping is
StreamableHTTPTransport#modern_http_status, which answers 400 for the codes inMODERN_BAD_REQUEST_CODES,-32600among them, and the existing transport tests cover it.Breaking Changes
None.
Types of changes
Checklist