refactor: make oauth discovery reactive#1052
Open
DaleSeo wants to merge 1 commit into
Open
Conversation
DaleSeo
force-pushed
the
refactor/reactive-oauth-discovery
branch
from
July 24, 2026 22:56
7d653d9 to
26b0a00
Compare
4 tasks
DaleSeo
marked this pull request as ready for review
July 24, 2026 23:15
DaleSeo
force-pushed
the
refactor/reactive-oauth-discovery
branch
from
July 24, 2026 23:56
26b0a00 to
1b06076
Compare
DaleSeo
force-pushed
the
refactor/reactive-oauth-discovery
branch
from
July 25, 2026 00:07
1b06076 to
3a18ab9
Compare
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.
Fixes #1048 at its root cause.
Motivation and Context
The POST probe, introduced in #960 to pass the client conformance suite, sends a synthetic JSON-RPC
initializerequest during discovery. Servers that accept it create sessions that are never cleaned up. Investigating the fix exposed a deeper structural issue.WWW-Authenticateheader on the client's real request. Well-known URIs are the fallback.404or405for a session-lessGETare still spec-compliant. In particular, the spec allows405for endpoints without SSE.This PR fixes the underlying issue instead of patching the probe by removing
initializePOST probe entirely.How Has This Been Tested?
Added tests
Breaking Changes
None
Types of changes
Checklist