<?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: mod_rewrite + mod_proxy + spaces in URI = boom!</title>
	<atom:link href="http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/</link>
	<description>What you get when you cross a programmer with a cyclist</description>
	<pubDate>Thu, 20 Nov 2008 06:23:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta1-9502</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bloutiouf</title>
		<link>http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/comment-page-1/#comment-684</link>
		<dc:creator>Bloutiouf</dc:creator>
		<pubDate>Sun, 10 Aug 2008 10:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/#comment-684</guid>
		<description>In fact the issue is solvable if you add a PHP file on your first server. Let me explain:

My site use "Search Engine Optimization" uri, i.e. "http://site/foo/barr" and not "http://site/index.php?firstarg=foo&#38;secondarg=bar". You can easily turn the second syntax into the first one. I mainly use the .htaccess file Joomla provides :

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/index.php
RewriteRule (.*) index.php/$1

In the file "index.php", you can access to the extra path with the variable $_SERVER['PATH_INFO']. For the example it would look like "/foo/bar". This string is not escaped. But you can do with the function urlencode. Then, but I didn't try, you can either put header('Location: http://newserveur'.urlencode($_SERVER['PATH_INFO'])) or put readfile('http://newserveur'.urlencode($_SERVER['PATH_INFO'])), I don't guess which is the correct, I think it depends if your SVN software understands header requests.

Here is. I hope this works :)</description>
		<content:encoded><![CDATA[<p>In fact the issue is solvable if you add a PHP file on your first server. Let me explain:</p>
<p>My site use &#8220;Search Engine Optimization&#8221; uri, i.e. &#8220;http://site/foo/barr&#8221; and not &#8220;http://site/index.php?firstarg=foo&amp;secondarg=bar&#8221;. You can easily turn the second syntax into the first one. I mainly use the .htaccess file Joomla provides :</p>
<p>RewriteEngine on<br />
RewriteCond %{REQUEST_FILENAME} !-f<br />
RewriteCond %{REQUEST_FILENAME} !-d<br />
RewriteCond %{REQUEST_URI} !^/index.php<br />
RewriteRule (.*) index.php/$1</p>
<p>In the file &#8220;index.php&#8221;, you can access to the extra path with the variable $_SERVER['PATH_INFO']. For the example it would look like &#8220;/foo/bar&#8221;. This string is not escaped. But you can do with the function urlencode. Then, but I didn&#8217;t try, you can either put header(&#8217;Location: <a href="http://newserveur" rel="nofollow">http://newserveur</a>&#8216;.urlencode($_SERVER['PATH_INFO'])) or put readfile(&#8217;http://newserveur&#8217;.urlencode($_SERVER['PATH_INFO'])), I don&#8217;t guess which is the correct, I think it depends if your SVN software understands header requests.</p>
<p>Here is. I hope this works <img src='http://www.buro9.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/comment-page-1/#comment-680</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 26 Jul 2008 19:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/#comment-680</guid>
		<description>That is nicely explained. Of course I only have access to .htaccess so I couldn't actually use it. I guess the issue is insolvable with only htaccess files.</description>
		<content:encoded><![CDATA[<p>That is nicely explained. Of course I only have access to .htaccess so I couldn&#8217;t actually use it. I guess the issue is insolvable with only htaccess files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
