1000 stream headers are sent split into two packets:
![Wireshark packet list](.img/packets.png)
>Interestingly, the RST_STREAM for stream 1051 doesn't fit in packet 15, so in packet 16 we see the server respond with a 404 response. Then in packet 17 the client does send the RST_STREAM, before moving on to sending the remaining 475 requests.
despite exceeding maximum number of advertised streams, the server never sends a RST_FRAME:
![No RST_STREAM frames from server](.img/ynoreset.png)
> No server RST_STREAM frames are seen in this trace, indicating that the server did not observe a concurrent stream violation.