Php return 500 code

Send a 500 Internal Server Error header with PHP.

This is a short guide on how to send a 500 Internal Server Error header to the client using PHP. This is useful because it allows us to tell the client that the server has encountered an unexpected condition and that it cannot fulfill the request.

Below, I have created a custom PHP function called internal_error.

//Function that sends a 500 Internal Server Error status code to //the client before killing the script. function internal_error()< header($_SERVER["SERVER_PROTOCOL"] . ' 500 Internal Server Error', true, 500); echo '
Something went wrong!
'; exit; >

When the PHP function above is called, the script’s execution is halted and “Something went wrong!” is printed out onto the page.

Furthermore, if you inspect the HTTP headers with your browser’s developer console, you will see that the function is returning a 500 Internal Server Error status code:

Google’s Developer Tools showing the 500 Internal Server Error status that was returned.

To send the 500 status code, we used PHP’s header function like so:

//Send a 500 status code using PHP's header function header($_SERVER["SERVER_PROTOCOL"] . ' 500 Internal Server Error', true, 500);

Note that we used the SERVER_PROTOCOL variable in this case because the client might be using HTTP 1.0 instead of HTTP 1.1. In other examples, you will find developers making the assumption that the client will always be using HTTP 1.1.

The problem with PHP is that it doesn’t always send a 500 Internal Server Error when an exception is thrown or a fatal error occurs.

This can cause a number of issues:

1. It becomes more difficult to handle failed Ajax calls, as the server in question is still responding with a 200 OK status. For example: The JQuery Ajax error handling functions will not be called.
2. Search engines such as Google may index your error pages. If this happens, your website may lose its rankings.
3. Other HTTP clients might think that everything is A-OK when it is not.

Note that if you are using PHP version 5.4 or above, you can use the http_response_code function:

//Using http_response_code http_response_code(500);

Источник

How can I get php to return 500 upon encountering a fatal exception?

Note: if you want to catch custom error type, which start with E_USER*, you can use function set_error_handler() to register error handler and trigger error by function trigger_error, however, this error handler can not handle E_ERROR error type. Solution 1: Solution 2: This is exactly the problem I had yesterday and I found solution as follows: 1) first of all, you need to catch PHP fatal errors, which is error type E_ERROR.

• How can I get php to return 500 upon encountering a fatal exception?
• How can I make PHP display the error instead of giving me 500 Internal Server Error [duplicate]
• HTTP Error 500.0 — Internal Server Error scriptProcessor could not be found in application configuration
• Error 500 when trying to use PHP FastCGI in Seven (IIS 7.5)
• How do I fix a 500 error in PHP?
• Why am I getting a 500 error on my HTTP request?
• Do I need to install php5-mysql first?

How can I get php to return 500 upon encountering a fatal exception?

PHP fatal errors come back as status code 200 to the HTTP client. How can I make it return a status code 500 (Internal server error)?

header("HTTP/1.1 500 Internal Server Error"); 

This is exactly the problem I had yesterday and I found solution as follows:

1) first of all, you need to catch PHP fatal errors, which is error type E_ERROR. when this error occurs, script will be stored the error and terminate execution. you can get the stored error by calling function error_get_last().

2) before script terminated, a callback function register_shutdown_function() will always be called. so you need to register a error handler by this function to do what you want, in this case, return header 500 and a customized internal error page (optional).

function my_error_handler() < $last_error = error_get_last(); if ($last_error && $last_error['type']==E_ERROR) < header("HTTP/1.1 500 Internal Server Error"); echo '. ';//html for 500 page >> register_shutdown_function('my_error_handler'); 

Note: if you want to catch custom error type, which start with E_USER*, you can use function set_error_handler() to register error handler and trigger error by function trigger_error, however, this error handler can not handle E_ERROR error type. see explanation on php.net about error handler

Standard PHP configuration does return 500 when error occurs! Just make sure that your display_errors = off. You can simulate it with:

ini_set('display_errors', 0); noFunction(); 

On production display_errors directive is off by default.

function handleException($ex) < error_log("Uncaught exception . get_class($ex) . " message=" . $ex->getMessage() . " line=" . $ex->getLine()); ob_end_clean(); # try to purge content sent so far header('HTTP/1.1 500 Internal Server Error'); echo 'Internal error'; > set_exception_handler('handleException'); 

Error 500 when trying to use PHP FastCGI in Seven (IIS, I tried lots of things to get this stupid server to work, gave all permissions to everyone to the web root folder and PHP folder and used the system account the the app pool. The command line version of PHP (just did a php.exe -info) seems to work fine.

How can I make PHP display the error instead of giving me 500 Internal Server Error [duplicate]

This has never happened before. Usually it displays the error, but now it just gives me a 500 Internal Server Error. Of course before, when it displayed the error, it was different servers. Now I’m on a new server (I have full root, so if I need to configure it somewhere in the php.ini, I can.) Or perhaps its something with Apache?

I’ve been putting up with it by just transferring the file to my other server and running it there to find the error, but that’s become too tedious. Is there a way to fix this?

Check the error_reporting , display_errors and display_startup_errors settings in your php.ini file. They should be set to E_ALL and «On» respectively (though you should not use display_errors on a production server, so disable this and use log_errors instead if/when you deploy it). You can also change these settings (except display_startup_errors ) at the very beginning of your script to set them at runtime (though you may not catch all errors this way):

error_reporting(E_ALL); ini_set('display_errors', 'On'); 

After that, restart server.

Use php -l (that’s an ‘L’) from the command line to output the syntax error that could be causing PHP to throw the status 500 error. It’ll output something like:

PHP Parse error: syntax error, unexpected ‘>’ in on line 18

It’s worth noting that if your error is due to .htaccess, for example a missing rewrite_module, you’ll still see the 500 internal Server Error.

is active (not a comment) somewhere else in the ini file.

My development server refused to display errors after upgrade to Kubuntu 16.04 — I had checked php.ini numerous times . turned out that there was a diplay_errors = off; about 100 lines below my

So remember the last one counts!

HTTP Error 500.0 — Internal Server Error, Well I tried reinstalling multiple times and no luck so far. Here is what I’ve done so far, reinstalled php mutiple times, double checked extension_dir path, added registry key under HKLM software php and added path for php.ini file, and have double checked other settings in php.ini.

HTTP Error 500.0 — Internal Server Error scriptProcessor could not be found in application configuration

I get this error when I attempt to open any php page.

scriptProcessor could not be found in application configuration

This is a brand new install of IIS, php, mysql, on Vista SP1

After trouble shooting for a little while I found out that if I attempt to run php-cgi.exe or php.exe a bunch of errors come up immediately stating it can’t find like 5 .dll files and reinstalling may fix the problem.—— Well I tried reinstalling multiple times and no luck so far

Here is what I’ve done so far, reinstalled php mutiple times, double checked extension_dir path, added registry key under HKLM software php and added path for php.ini file, and have double checked other settings in php.ini

Please look at this thread — you have not registered php-cgi.exe in the fastCgi section.

The above errors were the root of my cause, but while in my attempts to reinstall php the fastcgi was missing. I reinstalled php configured for fastcgi.

After much research and no clear answer. To fix my second error, I realized those .dll’s would have only been installed by other applications. For example, OCI would have only been there if I had oracle on the machine and so forth.

After a little trial and error commenting out extensions in the php.ini I got it working

Thanks for the help anilr, I wouldn’t have caught the fact that that other error.

Php — Ошибка сервера 500, Ask Question. 0. Сегодня ввёл в файл «config.php» некоторые изменения, и сайт стал недоступным, в чём проблема? Ошибка — …

Error 500 when trying to use PHP FastCGI in Seven (IIS 7.5)

I’m trying to install the PHP FastCGI module on an IIS 7.5 server, but could not succeed for some reason. I followed all the recommandations found in the different topics of this forums, but all I can end up with is an HTTP Error 500 :

C:\Program Files\PHP\php-cgi.exe — The FastCGI process exited unexpectedly

The advanced logging features gives me the following error message when invoking the PHP executable :

ModuleName	FastCgiModule
Notification	128
HttpStatus	500
HttpReason	Internal Server Error
HttpSubStatus	0
ErrorCode	255
ConfigExceptionInfo
Notification	EXECUTE_REQUEST_HANDLER
ErrorCode	The extended attributes are inconsistent. (0xff)

I tried lots of things to get this stupid server to work, gave all permissions to everyone to the web root folder and PHP folder and used the system account the the app pool. The command line version of PHP (just did a php.exe -info) seems to work fine. So I’m out of ideas here.

Maybe there’s a problem in IIS 7.5 and FastCGI ? Or do you have any suggestion to make this work ?

That’s weird. My IIS 7.5 box works as expected.

There must be some configuration missing, so please have a complete review of your IIS server configuration.

If you like, you can open a case via http://support.microsoft.com

How to send 500 Internal Server Error error from a PHP, Core Xii. 6,080 4 29 42. FYI, this solution sends the X-Pad: avoid browser bug header in some versions of Apache. stackoverflow.com/questions/8711584/… . http_response_code () omits this header. – Anthony Rutledge.

Источник