exit

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

exit — Terminar el script en curso con un código de estado o un mensaje

Descripción

exit(string|int $status = 0): never

Termina el script actual. Las funciones de cierre y los destructores de objetos siempre se ejecutarán incluso si exit es llamado. Sin embargo, los bloques finally nunca se ejecutan.

Un código de salida de 0 se utiliza para indicar que el programa ha completado sus tareas correctamente. Cualquier otro valor indica que ocurrió un error durante la ejecución.

exit() es una función especial, ya que dispone de un token dedicado en el analizador sintáctico. Puede ser utilizada como una instrucción (es decir, sin paréntesis) para terminar el script con el código de estado por defecto.

Precaución

No es posible desactivar o crear una función en un espacio de nombres que reemplace la función global exit().

Parámetros

status

Si status es un string, esta función muestra status justo antes de salir. El código de salida devuelto por PHP es 0.

Si status es un int, el código de salida devuelto por PHP será status.

Nota: Los códigos de salida deben estar comprendidos entre 0 y 254. El código de salida 255 está reservado por PHP y no debe ser utilizado.

Advertencia

Antes de PHP 8.4.0, exit() no respetaba la lógica habitual de manipulación de tipos de PHP ni la declaración strict_types.

Cualquier valor no int era convertido a string, incluyendo los valores de tipo resource y array. A partir de PHP 8.4.0, la función sigue la gestión estándar de tipos y genera una TypeError para los valores no válidos.

Valores devueltos

Como esta función termina el script PHP, ningún valor es devuelto.

Historial de cambios

Versión	Descripción
8.4.0	exit() es ahora una verdadera función, por lo tanto sigue la lógica habitual de manipulación de tipos, es afectada por la declaración `strict_types`, puede ser llamada con argumentos nombrados y ser utilizada como una función variable.

Ejemplos

Ejemplo #1 Ejemplo básico de la función exit()

<?php

// salir del programa normalmente
exit();
exit(0);

// salir con un código de error
exit(1);

?>

Ejemplo #2 Ejemplo de exit() con un string

<?php

$filename = '/path/to/data-file';
$file = fopen($filename, 'r')
    or exit("no se puede abrir el archivo ($filename)");
?>

Ejemplo #3 Ejemplo de ejecución de funciones de cierre y destructores de objetos

<?php
class Foo
{
    public function __destruct()
    {
        echo 'Destructor : ' . __METHOD__ . '()' . PHP_EOL;
    }
}

function shutdown()
{
    echo 'Cierre : ' . __FUNCTION__ . '()' . PHP_EOL;
}

$foo = new Foo();
register_shutdown_function('shutdown');

exit();
echo 'Esto nunca será mostrado.';
?>

El resultado del ejemplo sería:

Cierre : shutdown()
Destrucción : Foo::__destruct()

Ejemplo #4 exit() como instrucción

<?php

// salir del programa normalmente con el código de salida 0
exit;

?>

Notas

Advertencia

A partir de PHP 8.4.0, exit() era una construcción del lenguaje y no una función, por lo tanto no era posible llamarla utilizando funciones variables, o argumentos nombrados.

Ver también

register_shutdown_function() - Registra una función de retrollamada para ejecución al cierre
Funciones de cierre
destructores de objetos

Found A Problem?

Learn How To Improve This Page • Submit a Pull Request • Report a Bug

＋add a note

User Contributed Notes 14 notes

down

dexen dot devries at gmail dot com ¶

14 years ago

If you want to avoid calling exit() in FastCGI as per the comments below, but really, positively want to exit cleanly from nested function call or include, consider doing it the Python way:

define an exception named `SystemExit', throw it instead of calling exit() and catch it in index.php with an empty handler to finish script execution cleanly.

<?php

// file: index.php
class SystemExit extends Exception {}
try {
   /* code code */
}
catch (SystemExit $e) { /* do nothing */ }
// end of file: index.php

// some deeply nested function or .php file    

if (SOME_EXIT_CONDITION)
   throw new SystemExit(); // instead of exit()

?>

down

albert at removethis dot peschar dot net ¶

16 years ago

jbezorg at gmail proposed the following:

<?php

if($_SERVER['SCRIPT_FILENAME'] == __FILE__ )
  header('Location: /');

?>

After sending the `Location:' header PHP _will_ continue parsing, and all code below the header() call will still be executed.  So instead use:

<?php

if($_SERVER['SCRIPT_FILENAME'] == __FILE__)
{
  header('Location: /');
  exit;
}

?>

down

theonenkl at gmail dot com ¶

10 years ago

A side-note for the use of exit with finally: if you exit somewhere in a try block, the finally won't be executed. Could not sound obvious: for instance in Java you never issue an exit, at least a return in your controller; in PHP instead you could find yourself exiting from a controller method (e.g. in case you issue a redirect).

Here follows the POC:

<?php
echo "testing finally wit exit\n";

try {
    echo "In try, exiting\n";

    exit;
} catch(Exception $e) {
    echo "catched\n";
} finally {
    echo "in finally\n";
}

echo "In the end\n";
?>

This will print:

testing finally wit exit
In try, exiting

down

vincent dot laag at gmail dot com ¶

14 years ago

Don't use the  exit() function in the auto prepend file with fastcgi (linux/bsd os).
It has the effect of leaving opened files with for result at least a nice  "Too many open files  ..." error.

down

emils at tvnet dot lv ¶

21 years ago

Note, that using exit() will explicitly cause Roxen webserver to die, if PHP is used as Roxen SAPI module. There is no known workaround for that, except not to use exit(). CGI versions of PHP are not affected.

down

tianyiw at vip dot qq dot com ¶

2 years ago

These are the standard error codes in Linux or UNIX.

1 - Catchall for general errors
2 - Misuse of shell builtins (according to Bash documentation)
126 - Command invoked cannot execute
127 - “command not found”
128 - Invalid argument to exit
128+n - Fatal error signal “n”
130 - Script terminated by Control-C
255\* - Exit status out of range

down

void a t informance d o t info ¶

16 years ago

To rich dot lovely at klikzltd dot co dot uk:

Using a "@" before header() to suppress its error, and relying on the "headers already sent" error seems to me a very bad idea while building any serious website.

This is *not* a clean way to prevent a file from being called directly. At least this is not a secure method, as you rely on the presence of an exception sent by the parser at runtime.

I recommend using a more common way as defining a constant or assigning a variable with any value, and checking for its presence in the included script, like:

in index.php:
<?php
define ('INDEX', true);
?>

in your included file:
<?php
if (!defined('INDEX')) {
   die('You cannot call this script directly !');
}
?>

BR.

Ninj

down

chris at ocproducts dot com ¶

7 years ago

Calling 'exit' will bypass the auto_append_file option.
On some free hosting this risks you getting removed, as they may be using for ads and analytics.

So be a bit careful if using this on the most common output branch.

down

jean dot claveau at gmail dot com ¶

5 years ago

Beware if you enabled uopz extension, it disables exit / die() by default. They are just "skipped".

https://www.php.net/manual/en/function.uopz-allow-exit.php

down

devinemke at devinemke dot com ¶

23 years ago

If you are using templates with numerous includes then exit() will end you script and your template will not complete (no </table>, </body>, </html> etc...).  Rather than having complex nested conditional logic within your content, just create a "footer.php" file that closes all of your HTML and if you want to exit out of a script just include() the footer before you exit().

for example:

include ('header.php');
blah blah blah 
if (!$mysql_connect) {
echo "unable to connect";
include ('footer.php');
exit;
}
blah blah blah
include ('footer.php');

down

bill dot gates at hotmail dot com ¶

4 years ago

Be noticed about uopz (User Operations for Zend) extension of PHP. It disables (prevents) halting of PHP scripts (both FPM and CLI) on calling `exit()` and `die()` by default just after enabling the extension. Therefore your script will continue to execute.

Details: https://www.php.net/manual/en/uopz.configuration.php#ini.uopz.exit

down

alexyam at live dot com ¶

13 years ago

When using php-fpm, fastcgi_finish_request() should be used instead of register_shutdown_function() and exit()

For example, under nginx and php-fpm 5.3+, this will make browsers wait 10 seconds to show output:

<?php
    echo "You have to wait 10 seconds to see this.<br>";
    register_shutdown_function('shutdown');
    exit;
    function shutdown(){
        sleep(10);
        echo "Because exit() doesn't terminate php-fpm calls immediately.<br>";
    }
?>

This doesn't:

<?php
    echo "You can see this from the browser immediately.<br>";
    fastcgi_finish_request();
    sleep(10);
    echo "You can't see this form the browser.";
?>

down

m dot libergolis at gmail dot com ¶

9 years ago

In addition to "void a t informance d o t info", here's a one-liner that requires no constant:

<?php basename($_SERVER['PHP_SELF']) == basename(__FILE__) && die('Thou shall not pass!'); ?>

Placing it at the beginning of a PHP file will prevent direct access to the script.

To redirect to / instead of dying:

<?php
if (basename($_SERVER['PHP_SELF']) == basename(__FILE__)) {
    if (ob_get_contents()) ob_clean(); // ob_get_contents() even works without active output buffering
    header('Location: /');
    die;
}
?>

Doing the same in a one-liner:

<?php basename($_SERVER['PHP_SELF']) == basename(__FILE__) && (!ob_get_contents() || ob_clean()) && header('Location: /') && die; ?>

A note to security: Even though $_SERVER['PHP_SELF'] comes from the user, it's safe to assume its validity, as the "manipulation" takes place _before_ the actual file execution, meaning that the string _must_ have been valid enough to execute the file. Also, basename() is binary safe, so you can safely rely on this function.

down

sunfundev at gmail dot com ¶

7 years ago

>> Shutdown functions and object destructors will always be executed even if exit is called.

It is false if you call exit into desctructor.

Normal exit:
<?php
class A
{
    public function __destruct()
    {
        echo "bye A\n";
    }
}

class B
{
    public function __destruct()
    {
        echo "bye B\n";
    }
}

$a = new A;
$b = new B;
exit;

// Output:
// bye B
// bye A
?>

// Exit into desctructor:
<?php
class A
{
    public function __destruct()
    {
        echo "bye A\n";
    }
}

class B
{
    public function __destruct()
    {
        echo "bye B\n";
        exit;
    }
}

$a = new A;
$b = new B;

// Output:
// bye B
?>

＋add a note