Skip to content

Commit 1f82d0a

Browse files
committed
[#2422] Proofreading notes on output buffering and StreamedResponse
1 parent 678daba commit 1f82d0a

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

components/http_foundation/introduction.rst

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -389,15 +389,13 @@ represented by a PHP callable instead of a string::
389389

390390
.. note::
391391

392-
The ``flush()`` function does not flush bufferring. So if
393-
``ob_start()`` has been called before or php.ini option
394-
``output_buffering`` is not disabled (which is on some
395-
installations by default), you have to call ``ob_flush()`` before
396-
``flush()``.
397-
398-
But not only php can buffer output. Your web-server can also do
399-
it. Even more, if you use fastcgi, buffering can't be disabled at
400-
all.
392+
The ``flush()`` function does not flush buffering. If ``ob_start()`` has
393+
been called before or the ``output_buffering`` php.ini option is enabled,
394+
you must call ``ob_flush()`` before ``flush()``.
395+
396+
Additionally, PHP isn't the only layer that can buffer output. Your web
397+
server might also buffer based on its configuration. Even more, if you
398+
use fastcgi, buffering can't be disabled at all.
401399

402400
Downloading Files
403401
~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)