ob_flush
(PHP 4 >= 4.2.0, PHP 5)
ob_flush — Сброс (отправка) буфера вывода
Описание
void ob_flush
( void
)
Эта функция отправит содержимое буфера вывода (если имеется). Если необходима дальнейшая обработка буфера вывода, то следует вызвать ob_get_contents() перед ob_flush(), так как содержимое буфера будет удалено после вызова ob_flush().
Эта функция не уничтожает буфер вывода, как это делает ob_end_flush().
Возвращаемые значения
Эта функция не возвращает значения после выполнения.
Смотрите также
- ob_get_contents() - Возвращает содержимое буфера вывода
- ob_clean() - Очищает (стирает) буфер вывода
- ob_end_flush() - Сброс (отправка) буфера вывода и отключение буферизации вывода
- ob_end_clean() - Очищает (стирает) буфер вывода и отключает буферизацию вывода
Коментарии
I was having problems with output buffering which seemed to be active by default on the server, although phpinfo said something else..
In any case I needed to know that when I ran ob_start, it would start at the top level, so I could use ob_flush as it's intended without having to call multiple ob_flush in-script - this is what I did:
<?php
// make sure output buffering is off before we start it
// this will ensure same effect whether or not ob is enabled already
while (ob_get_level()) {
ob_end_flush();
}
// start output buffering
if (ob_get_length() === false) {
ob_start();
}
?>
Then I could call ob_flush(); followed by flush(); and get the output I wanted, which I didn't if I started the script with just ob_start();
This was on a windows apache 2 server with php 5.0.4 btw.
As stated in flush() manual entry, if php compresses the ouput with zlib this function may be ineffective.
A possible option for folders on your server that have scripts which may take a long time to run is to add the following in your relevant .htaccess file:
<FilesMatch "\.(php|html?)$">
php_flag zlib.output_compression off
php_value max_execution_time 3000
php_value max_input_time 3000
</FilesMatch>
If you call ob_flush() and flush() and still dont get the buffer flushed it might be because some antivirus software (Panda in this case) holds the buffer until the page has finished loaded before sending it to the browser.For some reason, calling just flush or ob_flush or even both together did not get my output buffers flushed, and calling ob_end_flush by itself didn't work either but calling them all worked well. Here is my new output flushing function.
<?php
function flush_buffers(){
ob_end_flush();
ob_flush();
flush();
ob_start();
}
?>
Enjoy
If you're still not getting the buffer work correctly then try to clean all the others before starting your own (and even if PHP tells you that there are no buffers active):
while(@ob_end_clean());
some problems with ob_flush() and flush() could be resolved by defining content type header :
header( 'Content-type: text/html; charset=utf-8' );
so working code looks like this:
<?php
header( 'Content-type: text/html; charset=utf-8' );
echo 'Begin ...<br />';
for( $i = 0 ; $i < 10 ; $i++ )
{
echo $i . '<br />';
flush();
ob_flush();
sleep(1);
}
echo 'End ...<br />';
?>
As of August 2012, all browsers seem to show an all-or-nothing approach to buffering. In other words, while php is operating, no content can be shown.
In particular this means that the following workarounds listed further down here are ineffective:
1) ob_flush (), flush () in any combination with other output buffering functions;
2) changes to php.ini involving setting output_buffer and/or zlib.output_compression to 0 or Off;
3) setting Apache variables such as "no-gzip" either through apache_setenv () or through entries in .htaccess.
So, until browsers begin to show buffered content again, the tips listed here are moot.
Although browsers now have an all or none buffering strategy, the arguments are not moot.
If you are not using ob_flush, you run this risk of exceeding socket timeouts (commonly seen in php-fpm/nginx combos).
Basically, flushing solves the infamous 504 Gateway Time-out error.
If there is no active output buffer, an error of level E_NOTICE is generated (at least in PHP 7.1). To avoid this, test first with `ob_get_level()`.The output buffer seems to work best when the server is returning a code 206 and setting the output_buffering lower temporarily to let it fill up
This tells the browser to wait for additional content
for example:
// Set the header to 206
header("HTTP/1.1 206 Partial Content; Content-Type: text/html; charset=utf-8");
// Flush the current outputbuffer
flush();
ob_flush();
ob_end_flush();
// Create a new output buffer
ob_start();
// Save the current output buffer size
$tempBuffering = ini_get("output_buffering");
// Set a new, much smaller buffer size
ini_set("output_buffering", 256);
// Do some buffering
!!! All your amazing code goes here !!!
// Fill the buffer with something if needed
echo str_pad(" ", (int)ini_get("output_buffering"), " ");
flush();
ob_flush();
// Revert the buffer size
ini_set("output_buffering", $tempBuffering);