PHP 8.1.28 Released!


(PHP 4, PHP 5, PHP 7, PHP 8)

ob_end_flushVolcar (enviar) el búfer de salida y deshabilitar el almacenamiento en el mismo


ob_end_flush(): bool

Esta función enviará el contenido del búfer de salida en cola (si existe) y los deshabilitará. Si fuera necesario procesar el contenido del búfer, se ha de llamar a ob_get_contents() antes que a ob_end_flush(), ya que el contenido del búfer es descartado después de llamar a ob_end_flush().

El búfer de salida debe estar iniciado por ob_start() con los indicadores PHP_OUTPUT_HANDLER_FLUSHABLE y PHP_OUTPUT_HANDLER_REMOVABLE Si no, ob_end_flush() no funcionará.

Nota: Esta función es similar a ob_get_flush(), excepto que ob_get_flush() devuelve el búfer como una cadena de caracteres.

Valores devueltos

Devuelve true en caso de éxito o false en caso de error. Entre las posibles razones de un fallo se encuentra llamar a la función sin un búfer activo, o que por algún motivo no se pueda eliminar un búfer (posible en el caso de búferes especiales).


Si la función falla, genera un error de nivel E_NOTICE.


Ejemplo #1 Ejemplo de ob_end_flush()

El siguiente ejemplo muestra una forma sencilla de volcar y finalizar todos los búferes de salida:

while (@ob_end_flush());

Ver también

  • ob_start() - Activa el almacenamiento en búfer de la salida
  • ob_get_contents() - Devolver el contenido del búfer de salida
  • ob_get_flush() - Volcar el búfer de salida, devolverlo como una cadena de caracteres y deshabilitar el almacenamiento en el búfer de salida
  • ob_flush() - Vaciar (enviar) el búfer de salida
  • ob_end_clean() - Limpiar (eliminar) el búfer de salida y deshabilitar el almacenamiento en el mismo

add a note

User Contributed Notes 10 notes

jhannus at 128kb dot com
19 years ago
A note on the above example...

with PHP 4 >= 4.2.0, PHP 5 you can use a combination of ob_get_level() and ob_end_flush() to avoid using the @ (error suppresion) which should probably be a little faaster.


while (ob_get_level() > 0) {

nico (at)
11 years ago
best way to compress a css code:

('Content-type: text/css');

compress($buffer) {
// remove comments
$buffer = preg_replace('!/\*[^*]*\*+([^/][^*]*\*+)*/!', '', $buffer);
// remove tabs, spaces, newlines, etc.
$buffer = str_replace(array("\r\n", "\r", "\n", "\t", ' ', ' ', ' '), '', $buffer);



Include in <head>:
<link rel="stylesheet" type="text/css" href="/design.php" media="all" />
anatoliy at miraline dot com
13 years ago
If you enable zlib.output_compression then level count will be increased by 1 and then this code:

<?php while (ob_get_level()) { ob_end_clean(); } ?>

will just freeze your script.
brett at realestate-school dot com
21 years ago
It appears that you can call ob_end_flush() regardless of whether or not output buffering was ever started using ob_start(). This can prove useful because it saves you from having to create conditional statements based on whether a particular function or include file has started output buffering. You can simply call the ob_end_flush() anyway and if there's output in the buffer, it will be sent, otherwise your script will just keep on keepin' on.
13 years ago
Wanted to speed things up and put some processing after the page has been delivered to the client. That drove me almost insane, but finally, I found a solution (php 5.2.5):

(); // outer buffer
ob_start(); // inner buffer to catch URL rewrites and other post processing
session_start(); // registers URL rewriter with inner buffer!
echo '...';
// log performance data to log files *after* delivering the page!
// now flush output output to client
// need to calculate content length *after* URL rewrite!
header("Content-length: ".ob_get_length());
// now we close the session and do some arbitrary clean-up tasks
// registered using register_shutdown_function()
skippy at zuavra dot net
18 years ago
Apart from being mostly redundant, ob_end_flush() can be downright damaging in some weird cases.

Actual example: a particular page on an Intranet website which would appear blank on Internet Explorer 6 when ob_start('ob_gzhandler') was called in the beginning and ob_end_flush() at the end.

We couldn't figure out what made that page special no matter what we tried. The ob_ functions were placed in scripts which were include()'d by all pages just the same, but only that page did this.

Even stranger, the problem only appeared on direct browser/server connections. Whenever the connection passed through a proxy the problem dissapeared. I'm guessing some kind of HTTP encoding headers mumbo-jumbo.

Solution: unless you really need it in particular cases, remove the ob_end_flush() call and rely on the builtin, automatic buffer flush.
4 months ago
NOTE: In IIS, flushing the output buffer doesnt work until you add the following to your web.config file under the PHP handler:


I discovered this when I would only get SSE output when the script failed.
14 years ago
It appears that ob_end_flush() is very important if you are looping. For instance if you are using a mass mailer that uses the output buffer for creating HTML content. Use ob_end_flush() to avoid server errors.
kriek at jonkriek dot com
21 years ago
ob_end_flush() isn't needed in MOST cases because it is called automatically at the end of script execution by PHP itself when output buffering is turned on either in the php.ini or by calling ob_start().
14 years ago
Remember that chromium browser (and maybe other webkit-based browsers) have some issues with ob_end_flush.

You may use
header("Content-Type: text/plain");
to solve those issues if you do not need html.
To Top