<?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>Tue, 18 Jun 2013 22:58:24 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Oscar Merida's Blog: Avoiding frustration with PHP Sessions]]></title>
      <guid>http://www.phpdeveloper.org/news/7536</guid>
      <link>http://www.phpdeveloper.org/news/7536</link>
      <description><![CDATA[<p>
On his blog, <i>Oscar Merida</i> has <a href="http://www.oscarm.org/news/detail/1877-avoiding_frustration_with_php_sessions">a quick new post</a> those just starting out with sessions should take a look at. He gives four quick tips of things to watch out for that can help your development process go smoother.
</p>
<blockquote>
PHP's support for sessions make adding "state" to your web application super easy.  Bus because the illusion of state is maintained by storing a Session ID via a user's cookies, you might find yourself losing potentially productive hours chasing down bizarre client side bugs or opening up a potential security hole.  Here are 4 tips to help you avoid wasting your time and securing your site.
</blockquote>
<p>
Items on the list are:
<ul>
<li>Don't use underscores in host names
<li>Commit your sessions before redirects
<li>Prevent session fixation (great security tip!)
<li>Don't expose session_id's
</ul>
Check out <a href="http://www.oscarm.org/news/detail/1877-avoiding_frustration_with_php_sessions">the comments</a> - there's some good recommendations in there as well.
</p>]]></description>
      <pubDate>Fri, 30 Mar 2007 11:28:00 -0500</pubDate>
    </item>
  </channel>
</rss>
