<?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 for Oliver's World of Research</title>
	<atom:link href="http://blog.ohohlfeld.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ohohlfeld.com</link>
	<description>Research</description>
	<pubDate>Tue, 06 Jan 2009 22:50:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Running WordPress behind Apache mod_proxy by Ronald</title>
		<link>http://blog.ohohlfeld.com/2008/06/infinite-301-redirect-loop-in-wordpress-due-to-canonical-urls-fixed/comment-page-1/#comment-839</link>
		<dc:creator>Ronald</dc:creator>
		<pubDate>Tue, 23 Dec 2008 02:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ohohlfeld.com/?p=41#comment-839</guid>
		<description>In Wordpress 2.7, this doesn't seem to fix the media uploader and some of the admin screens.</description>
		<content:encoded><![CDATA[<p>In Wordpress 2.7, this doesn&#8217;t seem to fix the media uploader and some of the admin screens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Running WordPress behind Apache mod_proxy by John</title>
		<link>http://blog.ohohlfeld.com/2008/06/infinite-301-redirect-loop-in-wordpress-due-to-canonical-urls-fixed/comment-page-1/#comment-71</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 24 Jun 2008 22:26:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ohohlfeld.com/?p=41#comment-71</guid>
		<description>Yes, this is a problem caused by mod_proxy. We're having the same trouble in our installation and I'm still fighting with Apache to issue the correct host name instead of putting it in X-Forwarded-Host. It doesn't seem to be an easy one and I'm looking forward to get some suggestions. I would think that this is a popper way to deal with it (instead of patching WP code, which fixes the issue, but only for one application).</description>
		<content:encoded><![CDATA[<p>Yes, this is a problem caused by mod_proxy. We&#8217;re having the same trouble in our installation and I&#8217;m still fighting with Apache to issue the correct host name instead of putting it in X-Forwarded-Host. It doesn&#8217;t seem to be an easy one and I&#8217;m looking forward to get some suggestions. I would think that this is a popper way to deal with it (instead of patching WP code, which fixes the issue, but only for one application).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<br />
<b>Warning</b>:  stristr() [<a href='function.stristr'>function.stristr</a>]: Empty delimiter. in <b>/home/oliver/public_html/ohcomblog/wp-content/plugins/wassup/wassup.php</b> on line <b>2093</b><br />
