From 29105fe8006c22a31c03a7b59425d980d179f4b1 Mon Sep 17 00:00:00 2001 From: Pierre-Yves Haubruge Date: Thu, 4 Sep 2025 01:26:41 +0200 Subject: [PATCH] fix missing word : page --- hosts/quic.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hosts/quic.rst b/hosts/quic.rst index 2ad531b..90159e3 100644 --- a/hosts/quic.rst +++ b/hosts/quic.rst @@ -603,7 +603,7 @@ Using this information, the receiver can easily reassemble the data received ove The penultimate frame shown in :numref:`fig-quic-streams-example` has the ``FIN`` flag set. It marks the end of stream ``1`` that has transported three bytes in total. The ``FIN`` flag is the normal way to gracefully close a QUIC stream. -There are however cases where an application might need to cancel a stream abruptly without closing the corresponding connection. First, the sending side of a stream can decide to reset the stream. For this, it sends a ``RESET_STREAM`` frame that carries the identifier of the stream that is canceled. The receiving side of a stream might also need to stop receiving data over a given stream. Consider for example a web browser that has started to download the different images that compose a web while the user has already clicked on another page from the same server. The streams that correspond to these images become useless. In this case, our browser can send a ``STOP_SENDING`` frame to indicate that it discards the incoming data over the corresponding streams. Upon reception of this frame, the server sends a ``RESET_STREAM`` frame to indicate that the corresponding stream has been closed. +There are however cases where an application might need to cancel a stream abruptly without closing the corresponding connection. First, the sending side of a stream can decide to reset the stream. For this, it sends a ``RESET_STREAM`` frame that carries the identifier of the stream that is canceled. The receiving side of a stream might also need to stop receiving data over a given stream. Consider for example a web browser that has started to download the different images that compose a web page while the user has already clicked on another page from the same server. The streams that correspond to these images become useless. In this case, our browser can send a ``STOP_SENDING`` frame to indicate that it discards the incoming data over the corresponding streams. Upon reception of this frame, the server sends a ``RESET_STREAM`` frame to indicate that the corresponding stream has been closed. .. exemple stop sending et reset stream ?