eval
In relation to the below comment, you may find that using the following may be more appropriate:
<?php
# ... user has pressed log out, cookies have been wiped, etc.
// Stay on the same page at time of logout (useful if a page is also available to anyone who isn't logged in
header ("Location: http://" . $_SERVER['HTTP_HOST'] . $_SERVER['PHP_SELF']);
?>
Of course $_SERVER['PHP_SELF'] can be omitted if you wish to redirect to the root directory of the site (http://www.example.com) or a path of your choosing can be used instead.
Alternatively, if you've a solid system implemented and logged out users can access the page too, you can continue with showing the page without using exit() or header().
exit
(PHP 4, PHP 5)
exit — Gibt eine Meldung aus und beendet das aktuelle Skript
Beschreibung
void exit
([ string
$status
] )
void exit
( int
$status
)Beendet die Ausführung des Skripts. Shutdown Funktionen und Objekt Destruktoren werden immer ausgeführt, auch wenn exit() aufgerufen wurde.
Parameter-Liste
-
status -
Falls
statuseine Zeichenkette ist, gibt diese Funktion beim Beenden denstatusaus.Falls
statuseine Ganzzahl ist, wird dieser Wert als Exit-Status verwendet anstatt ausgegeben zu werden. Ein Exit-Status sollte im Bereich von 0 bis 254 liegen, weil der Exit-Status 255 von PHP reserviert ist und deshalb nicht benutzt werden sollte. Der Status 0 wird verwendet, um ein Programm erfolgreich zu beenden.Hinweis: Falls
statuseine Ganzzahl ist, wird er von PHP >= 4.2.0 NICHT ausgegeben.
Rückgabewerte
Es wird kein Wert zurückgegeben.
Beispiele
Beispiel #1 exit()-Beispiel
<?php
$dateiname = '/pfad/zur/datei';
$datei = fopen($dateiname, 'r')
or exit("kann Datei $dateiname nicht öffnen");
?>
Beispiel #2 exit()-Status-Beispiel
<?php
// das Programm normal beenden
exit;
exit();
exit(0);
// das Programm mit einem Fehlercode beenden
exit(1);
exit(0376); // oktal
?>
Beispiel #3 Shutdown Funktionen und Destruktoren werden trotzdem aufgerufen
<?php
class Foo
{
public function __destruct()
{
echo 'Destruktor: ' . __METHOD__ . '()' . PHP_EOL;
}
}
function shutdown()
{
echo 'Shutdown Funktion: ' . __FUNCTION__ . '()' . PHP_EOL;
}
$foo = new Foo();
register_shutdown_function('shutdown');
exit();
echo 'Das hier wird nicht mehr ausgegeben werden.';
?>
Das oben gezeigte Beispiel erzeugt folgende Ausgabe:
Shutdown Funktion: shutdown() Destruktor: Foo::__destruct()
Anmerkungen
Hinweis: Da dies ein Sprachkonstrukt und keine Funktion ist, können Sie dieses nicht mit Variablenfunktionen verwenden.
Hinweis:
Dieses Sprachkonstrukt entspricht die().
Siehe auch
- register_shutdown_function() - Registriert eine Funktion zur Ausführung beim Skript-Abschluss
add a note
User Contributed Notesexit
dan
12-Jul-2007 12:11
12-Jul-2007 12:11
brianbtn at bellsouth dot net
11-May-2007 04:14
11-May-2007 04:14
how do I redirect back to the login page after someone clicks logout by using the passwordProtectedsite.php?logout=1
HERE IS THE CODE FROM PASSWORD_PROTECT.PHP
// logout?
if(isset($_GET['logout'])) {
setcookie("verify", '', $timeout, '/'); // clear password;
exit("Logged Out");
}
Roumen Semov
16-Feb-2006 08:54
16-Feb-2006 08:54
Please note in PHP "exit(0)" or simply "exit" returns true.
Any other value but zero will return false. This is good to know in case you are writing command-line php scripts where you need the result of the php script to determine if the next script will run. Example:
shell> ./my_php_script && echo "It ran successfully!"
If you know my_php_script can break somewhere you could do a conditional with an "exit(-1)" and then if the script breaks the command after the && will not execute.
09-Feb-2006 02:26
The note above is irrelevant, because a simple "return" would abort the template included by include or include_once!
francois at bonzon dot com
25-May-2005 03:42
25-May-2005 03:42
With output buffering on, when sending headers that shouldn't have any data after them, be sure to erase the buffer before exit()ing the script! Like this:
<?php
ob_clean();
exit();
?>
If you don't erase the buffer, in case it was not empty, after sending the headers PHP will still send the buffer content to the browser.
I had Firefox show strange behavior with some of my pages, that it took me quite some time to debug. It was simply because my script was returning 304 Not Modified headers along with the start of an HTML page.
nospam at mydomain dot com
27-Sep-2004 11:12
27-Sep-2004 11:12
Using return instead of exit is to prefer when you want the script that you have included inside another script to die but continue to execute the main script.
// Radcliff
emils at tvnet dot lv
23-Aug-2003 05:14
23-Aug-2003 05:14
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.
mbostrom at paragee dot com
26-Feb-2003 09:45
26-Feb-2003 09:45
In PHP 4.3.1 (and possibly 4.3.0), running scripts from the command line works a lot better. This is probably because 4.3.x has a whole new CLI mode.
Specifically, exit status is now returned (to the shell) as you would expect. This is a godsend for writing embedded email processing scripts, as much email infrastructure (fetchmail, qmail, mutt, etc.) is dependant upon correctly returned status codes, and the inability to return a status code (as in PHP 4.2.x) is an insurmountable obstacle.
$_SERVER["argv"] is also always available in 4.3.x, I think, whereas in 4.2.x php.ini could prevent it from being available.
(On the downside, I had to ./configure --without-mysql in order to get 4.3.1 to compile on RedHat 8.0. Otherwise there was what looked like a fatal compile warning (that I might also have been able to ignore somehow).
The "fatal warning" FYI:
ext/mysql/libmysql/my_tempnam.o: In function `my_tempnam':
ext/mysql/libmysql/my_tempnam.c:103: the use of `tempnam' is dangerous, better use `mkstemp'
Changing the code from tempnam to mkstemp would probably not be overly complicated, but it is non-trivial.)
shaun at NOshatSPAM dot net
09-Aug-2002 01:13
09-Aug-2002 01:13
return may be preferable to exit in certain situations, especially when dealing with the PHP binary and the shell.
I have a script which is the recipient of a mail alias, i.e. mail sent to that alias is piped to the script instead of being delivered to a mailbox. Using exit in this script resulted in the sender of the email getting a delivery failure notice. This was not the desired behavior, I wanted to silently discard messages which did not satisfy the script's requirements.
After several hours of trying to figure out what integer value I should pass to exit() to satisfy sendmail, I tried using return instead of exit. Worked like a charm. Sendmail didn't like exit but it was perfectly happy with return. So, if you're running into trouble with exit and other system binaries, try using return instead.
iamfast at tampabay dot rr dot com
14-Jul-2002 05:12
14-Jul-2002 05:12
If you are working with images or something of the sort that is not html, and use auto appending, call exit before you close your php tag, so that the footer is not included, corrupting the end of the file.
--Nate
devinemke at devinemke dot com
11-Jan-2002 09:38
11-Jan-2002 09:38
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');