<?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: MultiBlog</title>
	<atom:link href="https://rathercurious.no3.co.uk/archives/44/feed" rel="self" type="application/rss+xml" />
	<link>https://rathercurious.no3.co.uk/archives/44</link>
	<description>A home for my coding projects</description>
	<lastBuildDate>Fri, 26 Feb 2010 22:24:46 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.16</generator>
	<item>
		<title>By: Robert</title>
		<link>https://rathercurious.no3.co.uk/archives/44/comment-page-1#comment-496</link>
		<dc:creator><![CDATA[Robert]]></dc:creator>
		<pubDate>Mon, 14 Jul 2008 20:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://rathercurious.net/?p=44#comment-496</guid>
		<description><![CDATA[I think this would be a great idea.  I would think that this could potentially be done as a modified set of mod_rewrite rules.

Since wordpress currently uses a hard-coded site url we would also need to somehow change the site url on the fly.  This information may be stored in the database anyways so if we detect the url in advance then simply changing the database location (as you have suggested) should be sufficient.  I havn&#039;t checked the technical side of it.  All I know is when I went to access the blog via 192.168.1.1:8080 it re-routes to router.blah.org:8080 once the blog starts to load.

I did check the available php variables and $_SERVER[&quot;SERVER_NAME&quot;] should be safe.  I checked it on my lighttpd and apache installs and they both reported my server name (complete with port number if not on port 80).  Don&#039;t use the $_ENV sets because they were missing on my apache install.  Both use fastcgi.]]></description>
		<content:encoded><![CDATA[<p>I think this would be a great idea.  I would think that this could potentially be done as a modified set of mod_rewrite rules.</p>
<p>Since wordpress currently uses a hard-coded site url we would also need to somehow change the site url on the fly.  This information may be stored in the database anyways so if we detect the url in advance then simply changing the database location (as you have suggested) should be sufficient.  I havn&#8217;t checked the technical side of it.  All I know is when I went to access the blog via 192.168.1.1:8080 it re-routes to router.blah.org:8080 once the blog starts to load.</p>
<p>I did check the available php variables and $_SERVER["SERVER_NAME"] should be safe.  I checked it on my lighttpd and apache installs and they both reported my server name (complete with port number if not on port 80).  Don&#8217;t use the $_ENV sets because they were missing on my apache install.  Both use fastcgi.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
