<?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, 21 May 2013 16:36:07 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[VoucherTrader.co.uk Blog: A Further Problem With PHP Session IDs and Google]]></title>
      <guid>http://www.phpdeveloper.org/news/4651</guid>
      <link>http://www.phpdeveloper.org/news/4651</link>
      <description><![CDATA[On vouchertrader.co.uk today, there's <a href="http://www.vouchertrader.co.uk/blog/2006/01/11/a-further-problem-with-php-session-ids-and-google/">this look</a> at some more issues that can be caused by session IDs with the indexing that Google performs.
<p>
<quote>
<i>
While search for the VoucherTrader site in Google I noticed that the description for some pages was coming up as a PHP error about sessions. I actually thought I'd fixed this problem before by preventing PHP from creating sessions when the browsing user's user agent was the Googlebot. Unfortunately I was wrong...
</i>
</quote>
<p>
Come to find out, he <a href="http://www.vouchertrader.co.uk/blog/2006/01/11/a-further-problem-with-php-session-ids-and-google/">figured out</a> that, at the time the GoogleBot was coming through, the PHP install wasn't making a session for it. For a fix, he threw in a check to ensure that the user, based on the HTTP_USER_AGENT value, would start the session  correctly. The code is <a href="http://www.vouchertrader.co.uk/blog/2006/01/11/a-further-problem-with-php-session-ids-and-google/">included in the post</a>...]]></description>
      <pubDate>Thu, 12 Jan 2006 06:48:32 -0600</pubDate>
    </item>
  </channel>
</rss>
