ob_end_flush

(PHP 4, PHP 5)

ob_end_flush — Volcar (enviar) el búfer de salida y deshabilitar el uso del búfer

Descripción

bool ob_end_flush ( void )

Esta función enviará los contenidos del búfer de salida en cola (si existe) y deshabilita este búfer. Si desea procesar los contenidos del búfer es necesario que llame ob_get_contents() antes de ob_end_flush() ya que los contenidos del búfer son descartados después de llamar ob_end_flush().

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

Valores devueltos

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

Errores/Excepciones

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

Historial de cambios

Versión	Descripción
4.2.0	El valor de retorno booleano fue agregado.

Ejemplos

Ejemplo #1 Ejemplo de ob_end_flush()

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


<?php
  while (@ob_end_flush());
?>

Ver también

ob_start() - Turn on output buffering
ob_get_contents() - Devolver el contenido del búfer de salida
ob_get_flush() - Volcar el búfer de salida, devolverlo como una cadena y deshabilitar el uso de búferes de salida
ob_flush() - Vaciar (enviar) el búfer de salida
ob_end_clean() - Limpiar (eliminar) y deshabilitar los búferes de salida

ob_flush

ob_end_clean

[edit] Last updated: Fri, 25 May 2012

add a note User Contributed Notes ob_end_flush

anatoliy at miraline dot com 11-Apr-2011 09:06


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.

Mark 24-Jun-2010 01:49


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):





<?php


ob_start(); // 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!


register_shutdown_function(array($benchmarkclass,'log_perf_data'));


// now flush output output to client


ob_end_flush();


// need to calculate content length *after* URL rewrite!


header("Content-length: ".ob_get_length());


ob_end_flush();


// now we close the session and do some arbitrary clean-up tasks


// registered using register_shutdown_function()


session_write_close();


?>

unxed 06-Mar-2010 06:50


Remember that chromium browser (and maybe other webkit-based browsers) have some issues with ob_end_flush.



http://code.google.com/p/chromium/issues/detail?id=31410



You may use

header("Content-Type: text/plain");

to solve those issues if you do not need html.

shanep 21-Jan-2010 09:31


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.

skippy at zuavra dot net 01-Jul-2005 02:10


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.

jhannus at 128kb dot com 05-Jun-2004 09:18


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.



<?php



while (ob_get_level() > 0) {

    ob_end_flush();

}



?>

kriek at jonkriek dot com 29-Mar-2003 09:22


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().

brett at realestate-school dot com 26-Sep-2002 01:01


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.

add a note