<?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, 09 Jan 2009 06:42:09 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ian Selby's Blog: Uploading Large Files With PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/8656</guid>
      <link>http://www.phpdeveloper.org/news/8656</link>
      <description><![CDATA[<p>
<i>Ian Selby</i>, working for a startup and building a lot of code up from scratch <a href="http://www.gen-x-design.com/archives/uploading-large-files-with-php">came across a problem</a> - the upload of pretty large files via PHP:
</p>
<blockquote>
I have found myself in a position where I am writing scripts that may need to upload fairly large files. My scripts were timing out, and I couldn't seem to figure out why. For the unitiated, there are some standard things that you usually do to both your php.ini and in your script in this situation [...] However, it turns out there are some other php.ini config variables that you may need to look at.
</blockquote>
<p>
The "usual suspects" list includes changing the max_upload_size value and adjusting the script timeout. The other settings he mentions, though, are things like memory_limit, post_max_size and max_input_time to help increase the default times that PHP uses on most page executions.
</p>]]></description>
      <pubDate>Fri, 14 Sep 2007 13:03:54 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[CentreSource Blog: PHP Session Lifetime - an Adventure]]></title>
      <guid>http://www.phpdeveloper.org/news/5442</guid>
      <link>http://www.phpdeveloper.org/news/5442</link>
      <description><![CDATA[<p>
From the CentreBlog today, there's an <a href="http://blog.centresource.com/2006/05/23/php-session-lifetime-an-adventure/#more-484">in-depth look</a> at sessions as discovered by resolving a problem of prematurely expiring sessions on their apps.
</p>
<quote>
<i>
It started about two weeks ago, with no discernable changes to our configuration that could be responsible. So to understand what was necessary to track down this problem, we have to explore a little bit about how PHP session data storage and expiration works.
</i>
</quote>
<p>
They <a href="http://blog.centresource.com/2006/05/23/php-session-lifetime-an-adventure/#more-484">share</a> some of their discoveries, including:
<ul>
<li>the session.save_path setting in the php.ini tells the scripts where the sessions go
<li>garbage collection in PHP checks for sessions older than the session.gc_maxlifetime setting to remove
<li>but sessions were still expiring too early
</ul>
They finally started to Google for some answers and discovered that the problem wasn't in the default PHP configuration, the real issue was other software that overrode this php.ini value inside each execution. The result was that a script with the setting of 45 minutes would remove all sessions untouched for more than 45 minutes - regardless if they belonged to other software or not.
</p>]]></description>
      <pubDate>Wed, 24 May 2006 17:49:15 -0500</pubDate>
    </item>
  </channel>
</rss>
