<?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>Just another SharePoint developer blogging</description>
	<lastBuildDate>Wed, 01 Sep 2010 18:02:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/comment-page-1/#comment-829</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sat, 13 Feb 2010 15:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/#comment-829</guid>
		<description>Thank you for this article. I found it very helpful.</description>
		<content:encoded><![CDATA[<p>Thank you for this article. I found it very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rengler</title>
		<link>http://www.buro9.com/blog/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/comment-page-1/#comment-763</link>
		<dc:creator>rengler</dc:creator>
		<pubDate>Tue, 11 Aug 2009 00:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/08/17/mod_rewrite-mod_proxy-spaces-in-uri-boom/#comment-763</guid>
		<description>I&#039;m pretty sure this is the only website anywhere that details how to fix this problem. Thank you very much.

Separately, do you have any resources online that you consult for other tricks using mod_rewrite? I&#039;m having trouble writing a rule allowing Splunk on the side of my website.

Best...</description>
		<content:encoded><![CDATA[<p>I&#8217;m pretty sure this is the only website anywhere that details how to fix this problem. Thank you very much.</p>
<p>Separately, do you have any resources online that you consult for other tricks using mod_rewrite? I&#8217;m having trouble writing a rule allowing Splunk on the side of my website.</p>
<p>Best&#8230;</p>
]]></content:encoded>
	</item>
	<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 &quot;Search Engine Optimization&quot; uri, i.e. &quot;http://site/foo/barr&quot; and not &quot;http://site/index.php?firstarg=foo&amp;secondarg=bar&quot;. 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 &quot;index.php&quot;, you can access to the extra path with the variable $_SERVER[&#039;PATH_INFO&#039;]. For the example it would look like &quot;/foo/bar&quot;. This string is not escaped. But you can do with the function urlencode. Then, but I didn&#039;t try, you can either put header(&#039;Location: http://newserveur&#039;.urlencode($_SERVER[&#039;PATH_INFO&#039;])) or put readfile(&#039;http://newserveur&#039;.urlencode($_SERVER[&#039;PATH_INFO&#039;])), I don&#039;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(&#8216;Location: <a href="http://newserveur" rel="nofollow">http://newserveur</a>&#8216;.urlencode($_SERVER['PATH_INFO'])) or put readfile(&#8216;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 :)</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&#039;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>
