<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 15:15:49 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Gregory Szorc's Blog: PHP Now Using Proper HTTP Status Codes on Error]]></title>
      <guid>http://www.phpdeveloper.org/news/8521</guid>
      <link>http://www.phpdeveloper.org/news/8521</link>
      <description><![CDATA[<p>
<i>Gregory Szorc</i> writes today about a fact that's only recently come true in PHP's handling of errors - it seems that it now <a href="http://blog.case.edu/gps10/2007/08/23/php_now_using_proper_http_status_codes_on_error">returns proper HTTP status codes</a> when a problem comes up.
</p>
<blockquote>
If it encounters a serious error, like a parse error, it just stops and there is nothing you can do about it. If this happens on a hosted web site, you get a blank page served with the HTTP status code of 200. Completely useless to remote connections.
</blockquote>
<p>
This fix will be <a href="http://cvs.php.net/viewvc.cgi/php-src/NEWS?revision=PHP_5_2">included in the next version</a> of PHP - the upcoming 5.2.4 release. 
</p>]]></description>
      <pubDate>Thu, 23 Aug 2007 11:03:00 -0500</pubDate>
    </item>
  </channel>
</rss>
