<?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"
	>
<channel>
	<title>Comments on: Firefox vs. PRG</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/</link>
	<description>what was</description>
	<pubDate>Fri, 19 Mar 2010 13:10:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Mark Baker</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7984</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Tue, 06 Jun 2006 16:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7984</guid>
		<description>Yes, 302 is sometimes treated as being identical to 303, unfortunately, which is why 307 was created.  Still, 303 is better than 302 in this case because there's less ambiguity.</description>
		<content:encoded><![CDATA[<p>Yes, 302 is sometimes treated as being identical to 303, unfortunately, which is why 307 was created.  Still, 303 is better than 302 in this case because there&#8217;s less ambiguity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Baker</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7962</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Tue, 06 Jun 2006 12:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7962</guid>
		<description>Ouch, that's a bug.  The warning should show on a POST request that results in a 302 or 301 response.  As I say, 303 is the only http response code with PRG semantics.

I'll submit a bug when I get a chance.</description>
		<content:encoded><![CDATA[<p>Ouch, that&#8217;s a bug.  The warning should show on a POST request that results in a 302 or 301 response.  As I say, 303 is the only http response code with PRG semantics.</p>
<p>I&#8217;ll submit a bug when I get a chance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7930</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 05 Jun 2006 22:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7930</guid>
		<description>Thanks for catching that, Paul -- I've fixed the mangled attribute.</description>
		<content:encoded><![CDATA[<p>Thanks for catching that, Paul &#8212; I&#8217;ve fixed the mangled attribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Wilson</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7927</link>
		<dc:creator>Paul Wilson</dc:creator>
		<pubDate>Mon, 05 Jun 2006 21:23:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7927</guid>
		<description>Hi - the form is not rendering in Safari due to missing quote in "input" tag.  BTW all  working with PRG, on Firefox 1.5.0.4 on Mac (OS X 10.4)</description>
		<content:encoded><![CDATA[<p>Hi - the form is not rendering in Safari due to missing quote in &#8220;input&#8221; tag.  BTW all  working with PRG, on Firefox 1.5.0.4 on Mac (OS X 10.4)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7921</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 05 Jun 2006 19:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7921</guid>
		<description>&lt;p&gt;Since I updated Ubuntu on the weekend (same upstream Firefox version), PRG is working fine.  By default, PHP5 generates a 302 when I set a location header, but I see no difference with 303.&lt;/p&gt;

&lt;p&gt;For anyone else interested, I've put a small test online: &lt;a href="http://www.megginson.com/test/prg/prg-test.html" rel="nofollow"&gt;http://www.megginson.com/test/prg/prg-test.html&lt;/a&gt;.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Since I updated Ubuntu on the weekend (same upstream Firefox version), PRG is working fine.  By default, PHP5 generates a 302 when I set a location header, but I see no difference with 303.</p>
<p>For anyone else interested, I&#8217;ve put a small test online: <a href="http://www.megginson.com/test/prg/prg-test.html" rel="nofollow">http://www.megginson.com/test/prg/prg-test.html</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Baker</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7915</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Mon, 05 Jun 2006 18:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7915</guid>
		<description>Nobody's mentioned the response code, but I assume this is all using 303, right?  That's the only redirect response code with semantics that align with PRG as described.  If you were using 301 or 302, then Firefox's behaviour would be appropriate because that's telling the client to POST to a new URI, not - as with 303 - to find the results at some other URI.</description>
		<content:encoded><![CDATA[<p>Nobody&#8217;s mentioned the response code, but I assume this is all using 303, right?  That&#8217;s the only redirect response code with semantics that align with PRG as described.  If you were using 301 or 302, then Firefox&#8217;s behaviour would be appropriate because that&#8217;s telling the client to POST to a new URI, not - as with 303 - to find the results at some other URI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Helou</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-7912</link>
		<dc:creator>Jean Helou</dc:creator>
		<pubDate>Mon, 05 Jun 2006 16:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-7912</guid>
		<description>Same problem here on windows ... preventing us from using our selenium based tests :/</description>
		<content:encoded><![CDATA[<p>Same problem here on windows &#8230; preventing us from using our selenium based tests :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-6909</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 01 Jun 2006 12:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-6909</guid>
		<description>You saw the same as me, Aristotle?  If so, then it sounds like a bug specific to the Linux version. I'm glad to hear it's not a general practice.</description>
		<content:encoded><![CDATA[<p>You saw the same as me, Aristotle?  If so, then it sounds like a bug specific to the Linux version. I&#8217;m glad to hear it&#8217;s not a general practice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-6875</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Thu, 01 Jun 2006 01:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-6875</guid>
		<description>Whereas I can confirm seeing the same, using the following:

&lt;code&gt;Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Whereas I can confirm seeing the same, using the following:</p>
<p><code>Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Nokleberg</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/05/31/firefox-vs-prg/#comment-6828</link>
		<dc:creator>Chris Nokleberg</dc:creator>
		<pubDate>Wed, 31 May 2006 23:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/05/31/firefox-vs-prg/#comment-6828</guid>
		<description>I'm in the middle of developing a webapp that makes heavy use of P-R-G and that's not my experience with Firefox 1.5.0.3 (on Windows at least). Perhaps it is a bug triggered by certain headers in your redirect or something.</description>
		<content:encoded><![CDATA[<p>I&#8217;m in the middle of developing a webapp that makes heavy use of P-R-G and that&#8217;s not my experience with Firefox 1.5.0.3 (on Windows at least). Perhaps it is a bug triggered by certain headers in your redirect or something.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
