{"version":"2.1.232","anchor":"streaming-responses-stop-reading-as-soon-as-the-connection-c","canonical_anchor":"streaming-responses-stop-reading-as-soon-as-the-connection-c","heading":"Streaming responses stop reading as soon as the connection closes","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/streaming-responses-stop-reading-as-soon-as-the-connection-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Streaming responses stop reading as soon as the connection closes\n\nStreaming stops reading immediately when a connection closes instead of chewing through leftover events.\n\n**What**\n\nThe server-sent-events reader now checks whether the connection is closing or already closed, cancels the reader and leaves the loop instead of continuing to consume events. The same check runs inside per-event processing and in the connection-error handler.\n\n**Evidence**\n\n`isClosingOrClosed`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}