<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" 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/" > <channel><title>Comments on: Path_Info &amp; PHP_SELF woes [NginX]</title> <atom:link href="http://kbeezie.com/view/php-self-path-nginx/feed/" rel="self" type="application/rss+xml" /><link>http://kbeezie.com/view/php-self-path-nginx/</link> <description>There&#039;s no place like ::1</description> <lastBuildDate>Mon, 18 Apr 2011 01:47:04 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: kbeezie</title><link>http://kbeezie.com/view/php-self-path-nginx/#comment-1024</link> <dc:creator>kbeezie</dc:creator> <pubDate>Mon, 15 Nov 2010 17:49:01 +0000</pubDate> <guid isPermaLink="false">http://kbeezie.com/?p=208#comment-1024</guid> <description>Well that&#039;s not really *solving* it but rather taking a long work around. If you have the root defined in the server { } block and not location { } block then script filename would be automatic in the fastcgi params.</description> <content:encoded><![CDATA[<p>Well that&#8217;s not really *solving* it but rather taking a long work around. If you have the root defined in the server { } block and not location { } block then script filename would be automatic in the fastcgi params.</p> ]]></content:encoded> </item> <item><title>By: Matthew</title><link>http://kbeezie.com/view/php-self-path-nginx/#comment-1023</link> <dc:creator>Matthew</dc:creator> <pubDate>Mon, 15 Nov 2010 17:41:40 +0000</pubDate> <guid isPermaLink="false">http://kbeezie.com/?p=208#comment-1023</guid> <description>I replicated your config but my scripts were returning a 404 in the error log.  I had to have a SCRIPT_FILENAME manually configured for each vhost which solved the problem.</description> <content:encoded><![CDATA[<p>I replicated your config but my scripts were returning a 404 in the error log.  I had to have a SCRIPT_FILENAME manually configured for each vhost which solved the problem.</p> ]]></content:encoded> </item> <item><title>By: frostschutz</title><link>http://kbeezie.com/view/php-self-path-nginx/#comment-513</link> <dc:creator>frostschutz</dc:creator> <pubDate>Tue, 01 Jun 2010 09:36:20 +0000</pubDate> <guid isPermaLink="false">http://kbeezie.com/?p=208#comment-513</guid> <description>Also ran into a PHP security issue after following this guide (mainly because my php.conf did not include the folder restrictions anymore I had in place before).http://cnedelcu.blogspot.com/2010/05/nginx-php-via-fastcgi-important.htmlYes, I&#039;d prefer mod_rewrite over file.php/something too but unfortunately there are still a lot of scripts around that do this, both in Open Source and Proprietary scripts. :(</description> <content:encoded><![CDATA[<p>Also ran into a PHP security issue after following this guide (mainly because my php.conf did not include the folder restrictions anymore I had in place before).</p><p><a href="http://cnedelcu.blogspot.com/2010/05/nginx-php-via-fastcgi-important.html" rel="nofollow">http://cnedelcu.blogspot.com/2010/05/nginx-php-via-fastcgi-important.html</a></p><p>Yes, I&#8217;d prefer mod_rewrite over file.php/something too but unfortunately there are still a lot of scripts around that do this, both in Open Source and Proprietary scripts. <img src='http://kbeezie.net/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: kbeezie</title><link>http://kbeezie.com/view/php-self-path-nginx/#comment-511</link> <dc:creator>kbeezie</dc:creator> <pubDate>Mon, 31 May 2010 16:04:43 +0000</pubDate> <guid isPermaLink="false">http://kbeezie.com/?p=208#comment-511</guid> <description>When using paths after the php file name, PATH_INFO should show up as the path trailing the script, I would assume this should be the same for PATH_TRANSLATED as well when using a path trailing the file name. I do however advise that people concentrate on parsing the REQUEST_URI as opposed to relying on PATH_INFO and PATH_TRANSLATED. Most systems now days use mod_rewrite or similar and use the request_uri instead of the older path_info.</description> <content:encoded><![CDATA[<p>When using paths after the php file name, PATH_INFO should show up as the path trailing the script, I would assume this should be the same for PATH_TRANSLATED as well when using a path trailing the file name. I do however advise that people concentrate on parsing the REQUEST_URI as opposed to relying on PATH_INFO and PATH_TRANSLATED. Most systems now days use mod_rewrite or similar and use the request_uri instead of the older path_info.</p> ]]></content:encoded> </item> <item><title>By: frostschutz</title><link>http://kbeezie.com/view/php-self-path-nginx/#comment-509</link> <dc:creator>frostschutz</dc:creator> <pubDate>Thu, 27 May 2010 09:19:47 +0000</pubDate> <guid isPermaLink="false">http://kbeezie.com/?p=208#comment-509</guid> <description>First of all, thanks for sharing this! I&#039;ve successfully replicated your setup, and for /php.php/a/path/string/?var=foo I get the same results as you. I do have a question however:What should the expected result be if php.php is in a subfolder, i.e. /folder/php.php/a/path/string/?var=foo?Currently, PATH_TRANSLATED for /php.php/ and /folder/php.php/ is exactly the same, I wonder if this is indeed correct or if /folder/ should go in there too.</description> <content:encoded><![CDATA[<p>First of all, thanks for sharing this! I&#8217;ve successfully replicated your setup, and for /php.php/a/path/string/?var=foo I get the same results as you. I do have a question however:</p><p>What should the expected result be if php.php is in a subfolder, i.e. /folder/php.php/a/path/string/?var=foo?</p><p>Currently, PATH_TRANSLATED for /php.php/ and /folder/php.php/ is exactly the same, I wonder if this is indeed correct or if /folder/ should go in there too.</p> ]]></content:encoded> </item> </channel> </rss>
