Repository navigation
Allow stateful HTTP endpoints to recover after DELETE - #307
Open
EhsanAzish80 wants to merge 1 commit into
Open
EhsanAzish80 wants to merge 1 commit into
EhsanAzish80 wants to merge 1 commit into
Conversation
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 #286 for stateful HTTP endpoints. A
StatefulHTTPServerTransporthandles one session; the new session manager creates a fresh server and transport for each initialize. The built-in HTTP app uses it, stops the old server after DELETE, and returns 404 for the retired session ID.Tests: 561 Swift tests passed. A real HTTP loopback passed initialize → DELETE → new initialize with a different session ID, then 404 for the old ID. The 2025 server-initialize conformance scenario passed 3/3.
AI was used to write the tests. I ran them locally.