<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pacecode Blog &#187; server configuration</title>
	<atom:link href="http://www.pacecode.com/blog/category/server-configuration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pacecode.com/blog</link>
	<description>Tips, Scripts and More...</description>
	<lastBuildDate>Sat, 03 Dec 2011 09:45:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Magic with htaccess file &#8211; Increase execution time, session expiry time and file upload size limit</title>
		<link>http://www.pacecode.com/blog/2008/09/22/magic-with-htaccess-file-increase-execution-time-session-expiry-time-and-file-upload-size-limit/</link>
		<comments>http://www.pacecode.com/blog/2008/09/22/magic-with-htaccess-file-increase-execution-time-session-expiry-time-and-file-upload-size-limit/#comments</comments>
		<pubDate>Mon, 22 Sep 2008 17:38:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[htaccess]]></category>
		<category><![CDATA[server configuration]]></category>
		<category><![CDATA[all in one htaccess process]]></category>
		<category><![CDATA[handling server variable with htaccess]]></category>
		<category><![CDATA[htaccess and php ini]]></category>
		<category><![CDATA[htaccess for file execution time]]></category>
		<category><![CDATA[htaccess for file upload limit]]></category>
		<category><![CDATA[htaccess for sesssion expiry]]></category>
		<category><![CDATA[htaccess to increase memory limit]]></category>
		<category><![CDATA[magic with htaccess]]></category>
		<category><![CDATA[server configuration file changes with htaccess]]></category>

		<guid isPermaLink="false">http://www.pacecode.com/blog/?p=13</guid>
		<description><![CDATA[&#60;IfModule mod_php5.c&#62; php_value post_max_size 5M php_value upload_max_filesize 5M php_value memory_limit 300M php_value max_execution_time 259200 php_value max_input_time 259200 php_value session.gc_maxlifetime 1200 &#60;/IfModule&#62; php_value memory_limit 300M - Set higher default php_value memory_limit in .htaccess upload_max_filesize 5M - it increases default upload limit. The default upload limit is 2MB. the above htaccess increase increases file limit 2mb to [...]]]></description>
			<content:encoded><![CDATA[<p>&lt;IfModule mod_php5.c&gt;<br />
php_value post_max_size 5M<br />
php_value upload_max_filesize 5M<br />
php_value memory_limit 300M<br />
php_value max_execution_time 259200<br />
php_value max_input_time 259200<br />
php_value session.gc_maxlifetime 1200<br />
&lt;/IfModule&gt;</p>
<p><strong>php_value memory_limit 300M</strong> - Set higher default php_value memory_limit in .htaccess</p>
<p><strong>upload_max_filesize 5M </strong>- it increases default upload limit. The default upload limit is 2MB. the above htaccess increase increases file limit 2mb to 5 mb</p>
<p><strong>php_value max_execution_time: </strong></p>
<p>Set the number of seconds a script is allowed to run. If this is reached,<br />
the script returns a fatal error. The default limit is 30 seconds or, if it<br />
exists, the max_execution_time value defined in the configuration file. If<br />
seconds is set to zero, no time limit is imposed.</p>
<p><strong>php_value session.gc_maxlifetime: </strong></p>
<p>The session.gc_maxlifetime only sets the age of the session files that will be deleted when</p>
<p>garbage collection runs.</p>
<p>If you have a busy web site with a lot of sessions being created, garbage collection will</p>
<p>run based on session.gc_probability/session.gc_divisor. Despite this being called</p>
<p>"probability" I tested this and it is strictly a count. Using the default</p>
<p>gc_probability/gc_divisor of 1/100, this means that garbage collection will run every 100</p>
<p>new sessions (Edit: Actually this occurs within the session_start() coding and would count</p>
<p>re-started sessions as well) and delete any existing session files that are older than the</p>
<p>session.gc_maxlifetime. There is no file locking on the session files, so active session</p>
<p>files will be deleted and things like users getting logged out will occur.</p>
<p>If this is on shared hosting and the session files are all kept in the default location and</p>
<p>someone else is using a smaller session.gc_maxlifetime or a more frequent</p>
<p>gc_probability/gc_divisor, then any of the session files will get deleted based on the</p>
<p>lowest value of gc_maxlifetime and the most frequent gc_probability/gc_divisor.</p>
<p>You need to increase session.gc_maxlifetime or make session.gc_divisor larger and if this is</p>
<p>on shared hosting, set session.save_path to be a location within your web space.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pacecode.com/blog/2008/09/22/magic-with-htaccess-file-increase-execution-time-session-expiry-time-and-file-upload-size-limit/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

