<?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>Fri, 24 May 2013 06:17:53 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brian Moon's Blog: ob_start and HTTP headers]]></title>
      <guid>http://www.phpdeveloper.org/news/13947</guid>
      <link>http://www.phpdeveloper.org/news/13947</link>
      <description><![CDATA[<p>
<i>Brian Moon</i> has a new post to his blog today looking at something it's common for web applications to use, <a href="http://php.net/ob_start">ob_start</a>, and <a href="http://brian.moonspot.net/php-ob-start-headers">what about HTTP headers</a> makes it work to prevent the infamous "headers already sent" message.
</p>
<blockquote>
HTTP is the communication protocol that happens between your web server and the user's browser.  Without too much detail, this is broken into two pieces of data: headers and the body.  The body is the HTML you send. But, before the body is sent, the HTTP headers are sent.
</blockquote>
<p>
He includes a sample raw HTTP response for a page and how the <a href="http://php.net/ob_start">ob_start</a> function works to buffer the output of the resulting page to save the header information until the buffer is echoed or cleaned out. There is a down side he mentions, though - there's no partial buffering built in so it's an all or nothing short.
</p>]]></description>
      <pubDate>Mon, 01 Feb 2010 14:38:27 -0600</pubDate>
    </item>
  </channel>
</rss>
