﻿<?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 Geek Induldence</title>
	<atom:link href="http://geekindulgence.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://geekindulgence.com</link>
	<description>Development. Technology. Life.</description>
	<lastBuildDate>Sat, 30 Jul 2011 20:28:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>Comment on Glimpse + AppHarbor = Sad Face :( by Andrew Ma</title>
		<link>http://geekindulgence.com/2011/07/05/glimpse-appharbor-sad-face/#comment-8</link>
		<dc:creator>Andrew Ma</dc:creator>
		<pubDate>Sat, 30 Jul 2011 20:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.geekindulgence.com/?p=22#comment-8</guid>
		<description>Looks like this was resolved. Details here: https://github.com/Glimpse/Glimpse/pull/88</description>
		<content:encoded><![CDATA[<p>Looks like this was resolved. Details here: <a href="https://github.com/Glimpse/Glimpse/pull/88" rel="nofollow">https://github.com/Glimpse/Glimpse/pull/88</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Glimpse + AppHarbor = Sad Face :( by Troels Thomsen</title>
		<link>http://geekindulgence.com/2011/07/05/glimpse-appharbor-sad-face/#comment-2</link>
		<dc:creator>Troels Thomsen</dc:creator>
		<pubDate>Thu, 07 Jul 2011 21:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.geekindulgence.com/?p=22#comment-2</guid>
		<description>I would recommend going with the X-Forwarded-For header. It is true that this could potentially break in other environments, but it is still the de facto standard when working with load-balancing.

In case you&#039;re worried about the risk, you could add a variable on AppHarbor that gets injected to the configuration file. If this variable isn&#039;t set, you can avoid considering the X-Forwarded-For header.</description>
		<content:encoded><![CDATA[<p>I would recommend going with the X-Forwarded-For header. It is true that this could potentially break in other environments, but it is still the de facto standard when working with load-balancing.</p>
<p>In case you&#8217;re worried about the risk, you could add a variable on AppHarbor that gets injected to the configuration file. If this variable isn&#8217;t set, you can avoid considering the X-Forwarded-For header.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

