 
<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Reverse Proxy Fix plugin</title>
	<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/</link>
	<description>professional web development and consulting</description>
	<pubDate>Fri, 21 Nov 2008 05:38:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Brian</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-14198</link>
		<pubDate>Mon, 29 Sep 2008 19:12:36 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-14198</guid>
					<description>@Stefano
I'd need to know more about your situation. Hit up the support form on the site (under "contact and support") and give me some more details.  I have about 10 Rails 2.1 sites that are using the plugin without issue.</description>
		<content:encoded><![CDATA[<p>@Stefano<br />
I&#8217;d need to know more about your situation. Hit up the support form on the site (under &#8220;contact and support&#8221;) and give me some more details.  I have about 10 Rails 2.1 sites that are using the plugin without issue.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hatem</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13677</link>
		<pubDate>Tue, 16 Sep 2008 08:23:23 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13677</guid>
					<description>Hi, I have a question about Ruby on Rails sessions.

I'm planning to use a reverse proxy on production. When I use Firebug to watch the response headers, I see that a header of "Set-Cookie" is set with the same session id on every request.

Now, with every request from the same user, the reverse proxy will always think it is a new session and hence prevent caching and affect the performance.

Can you help me to fix this?
Thank you.</description>
		<content:encoded><![CDATA[<p>Hi, I have a question about Ruby on Rails sessions.</p>
<p>I&#8217;m planning to use a reverse proxy on production. When I use Firebug to watch the response headers, I see that a header of &#8220;Set-Cookie&#8221; is set with the same session id on every request.</p>
<p>Now, with every request from the same user, the reverse proxy will always think it is a new session and hence prevent caching and affect the performance.</p>
<p>Can you help me to fix this?<br />
Thank you.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stefano Palma</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13441</link>
		<pubDate>Tue, 09 Sep 2008 14:15:27 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13441</guid>
					<description>Brian,
I’ve installed your fix for Rails 2.0, but I’m using Rails 2.1 and it seems it doesn’t work. Any suggestions?
Thanks
Stefano</description>
		<content:encoded><![CDATA[<p>Brian,<br />
I’ve installed your fix for Rails 2.0, but I’m using Rails 2.1 and it seems it doesn’t work. Any suggestions?<br />
Thanks<br />
Stefano
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stefano Palma</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13400</link>
		<pubDate>Mon, 08 Sep 2008 12:18:24 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13400</guid>
					<description>Brian,
I've installed your fix for Rails 2.0, but I'm using Rails 2.1 and it seems it doesn't work. Any suggestions?
Thanks
Stefano</description>
		<content:encoded><![CDATA[<p>Brian,<br />
I&#8217;ve installed your fix for Rails 2.0, but I&#8217;m using Rails 2.1 and it seems it doesn&#8217;t work. Any suggestions?<br />
Thanks<br />
Stefano
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brian</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-7544</link>
		<pubDate>Sat, 08 Mar 2008 00:10:29 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-7544</guid>
					<description>@Eric:

You are correct. Name routing doesn't work with Reverse Proxy Fix in Rails 2.0 because they don't make named routes go through the same process. I have a fix and will get it out to the repository tonight. 

Thanks for pointing this out.</description>
		<content:encoded><![CDATA[<p>@Eric:</p>
<p>You are correct. Name routing doesn&#8217;t work with Reverse Proxy Fix in Rails 2.0 because they don&#8217;t make named routes go through the same process. I have a fix and will get it out to the repository tonight. </p>
<p>Thanks for pointing this out.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eric Young</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-7530</link>
		<pubDate>Fri, 07 Mar 2008 09:42:03 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-7530</guid>
					<description>I've just been playing with remapping redmine and a couple of the named routes,
  map.signin 'login', :controller =&#62; 'account', :action =&#62; 'login'
  map.signout 'logout', :controller =&#62; 'account', :action =&#62; 'logout'
are not being remapped by reverse_proxy_fix.  Everything else seems to work fine, just the named routes do not.  Any ideas?  I'm on rails 2.0 I believe.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just been playing with remapping redmine and a couple of the named routes,<br />
  map.signin &#8216;login&#8217;, :controller =&gt; &#8216;account&#8217;, :action =&gt; &#8216;login&#8217;<br />
  map.signout &#8216;logout&#8217;, :controller =&gt; &#8216;account&#8217;, :action =&gt; &#8216;logout&#8217;<br />
are not being remapped by reverse_proxy_fix.  Everything else seems to work fine, just the named routes do not.  Any ideas?  I&#8217;m on rails 2.0 I believe.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brian</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-56</link>
		<pubDate>Mon, 13 Nov 2006 14:12:28 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-56</guid>
					<description>@Detlef:

Not sure how you installed it, but all methods that use url_for are supported by this plugin. That includes link_to, link_to_unless_current, and others. However, you have to use the url_for method of constructing your links.

link_to "something", :controller =&gt;"foo", :action=&gt;"bar", :id=&gt;"1" will work.  

link_to "something", "/foo/bar" probably will not.</description>
		<content:encoded><![CDATA[<p>@Detlef:</p>
<p>Not sure how you installed it, but all methods that use url_for are supported by this plugin. That includes link_to, link_to_unless_current, and others. However, you have to use the url_for method of constructing your links.</p>
<p>link_to &#8220;something&#8221;, :controller =>&#8221;foo&#8221;, :action=>&#8221;bar&#8221;, :id=>&#8221;1&#8243; will work.  </p>
<p>link_to &#8220;something&#8221;, &#8220;/foo/bar&#8221; probably will not.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Detlef Werner</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-22</link>
		<pubDate>Wed, 18 Oct 2006 06:18:14 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-22</guid>
					<description>Brian, 
we tried this plugin, however only with partial success. While stylesheets via stylesheet_link_tag in layout are corrected, the normal link_to in views remains uncorrected. Is link_to not supported?
Regards
    detlef</description>
		<content:encoded><![CDATA[<p>Brian,<br />
we tried this plugin, however only with partial success. While stylesheets via stylesheet_link_tag in layout are corrected, the normal link_to in views remains uncorrected. Is link_to not supported?<br />
Regards<br />
    detlef
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brian</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13</link>
		<pubDate>Mon, 25 Sep 2006 21:01:56 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-13</guid>
					<description>@Bart:

I used relative_uri_root originally and discovered that it left a few things out. It's been so long that I cannot remember exactly what the issues were. Thanks for giving me something to revisit.</description>
		<content:encoded><![CDATA[<p>@Bart:</p>
<p>I used relative_uri_root originally and discovered that it left a few things out. It&#8217;s been so long that I cannot remember exactly what the issues were. Thanks for giving me something to revisit.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bart Braem</title>
		<link>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-11</link>
		<pubDate>Sat, 23 Sep 2006 16:58:24 +0000</pubDate>
		<guid>http://www.napcsweb.com/blog/2006/05/10/reverse-proxy-fix-plugin/#comment-11</guid>
					<description>I wonder, how is this different from setting relative_url_root?</description>
		<content:encoded><![CDATA[<p>I wonder, how is this different from setting relative_url_root?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
