You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RST immediately terminates a stream from any state. Both sides SHOULD release stream resources upon sending or receiving RST. No further frames SHOULD be sent on a reset stream.
181
+
This allows FIN to delimit messages within a long-lived stream.
184
182
185
183
## 6. Flow Control
186
184
@@ -195,6 +193,7 @@ Each stream maintains an independent receive window representing the number of b
195
193
**Behavior:**
196
194
- Senders MUST NOT send more data than the receiver's advertised window.
197
195
- Each byte of Data payload consumes one byte of window.
196
+
- Each FIN marker consumes 32 bytes of window (to prevent FIN spam attacks).
198
197
- Window Update frames replenish the window.
199
198
200
199
### 6.2 Window Updates
@@ -267,7 +266,7 @@ Upon detecting a protocol violation, implementations MUST:
267
266
268
267
### 8.2 Stream Errors vs Connection Errors
269
268
270
-
-**Stream errors** (e.g., application-level errors) SHOULD be handled with RST on that stream.
269
+
-**Stream errors** (e.g., application-level errors) are handled by the application dropping the stream handle. The remote peer is not explicitly notified.
271
270
-**Connection errors** (e.g., protocol violations) MUST be handled with GoAway and connection closure.
0 commit comments