|
|
|
|
Bookmark this on Delicious
Share on Facebook
 Slashdot It!
Digg  exit
Output a message and terminate the current script
(PHP 4, PHP 5)
Example 1355. exit() example<?phpExample 1356. exit() status example<?phpRelated Examples ( Source code ) » exit Examples ( Source code ) » Authenticate user Examples ( Source code ) » Prompt Browser password dialog Examples ( Source code ) » Open browser password dialog and authenticate user based on database Examples ( Source code ) » File based login Examples ( Source code ) » Login form with Error Messages and Preserving User Input Examples ( Source code ) » Delete data from database table Examples ( Source code ) » Create table and install data Examples ( Source code ) » String compare with if statement Examples ( Source code ) » Stopping Page Execution Examples ( Source code ) » Execute several HttpRequests in parallel Examples ( Source code ) » Posting a file / image to twitpic.com using PHP and cUrl Code Examples / Notes » exitfrancois
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
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 09-feb-2006 01:26
The note above is irrelevant, because a simple "return" would abort the template included by include or include_once!
shaun
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. roumen semov
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. emils
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.
dan
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(). mbostrom
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.) iamfast
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
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'); brianbtn
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"); } |
