Decide whether a finished POST response must be suppressed because the client
disconnected mid-request. On the draft Streamable HTTP transport a client
disconnect IS the cancellation signal (draft basic/utilities/cancellation
§Transport-Specific Cancellation: "Closing the SSE response stream is the
cancellation signal. The server MUST treat a client disconnect as cancellation
of that request. No notifications/cancelled message is required or expected.").
So when the connection has dropped on a draft request, the response is
suppressed. Released versions (2025-*) never suppress on this basis: that MUST
is draft-only, so their wire behaviour is unchanged.
Decide whether a finished POST response must be suppressed because the client disconnected mid-request. On the draft Streamable HTTP transport a client disconnect IS the cancellation signal (draft basic/utilities/cancellation §Transport-Specific Cancellation: "Closing the SSE response stream is the cancellation signal. The server MUST treat a client disconnect as cancellation of that request. No notifications/cancelled message is required or expected."). So when the connection has dropped on a draft request, the response is suppressed. Released versions (2025-*) never suppress on this basis: that MUST is draft-only, so their wire behaviour is unchanged.