Comments on: “Browse by Name” And Firefox http://journal.adityamukherjee.com/essay/browse-by-name-and-firefox/ Warning: Geek Inside! Mon, 26 Oct 2009 08:14:55 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Aditya http://journal.adityamukherjee.com/essay/browse-by-name-and-firefox/comment-page-1/#comment-1783 Aditya Tue, 29 Jul 2008 04:50:01 +0000 http://adityamukherjee.com/geekaholic/?p=776#comment-1783 <p>Stephen » The 302 header can be justified. In Google's defence, the final URL being pointed to might change tomorrow, so the "temporarily moved" header is probably the right way to go. 303 is phrased as "see also", which it actually isn't - if we take Google's context.</p> <p>It's a matter of perception really, and either Google or Firefox can be right. I personally would like to see an extension, or a Firefox option that would atleast give us the chance to alter the default behaviour.</p> <p>(even an about:config key would do)</p> Stephen » The 302 header can be justified. In Google’s defence, the final URL being pointed to might change tomorrow, so the “temporarily moved” header is probably the right way to go. 303 is phrased as “see also”, which it actually isn’t - if we take Google’s context.

It’s a matter of perception really, and either Google or Firefox can be right. I personally would like to see an extension, or a Firefox option that would atleast give us the chance to alter the default behaviour.

(even an about:config key would do)

]]> By: Stephen Paul Weber http://journal.adityamukherjee.com/essay/browse-by-name-and-firefox/comment-page-1/#comment-1767 Stephen Paul Weber Mon, 28 Jul 2008 21:24:55 +0000 http://adityamukherjee.com/geekaholic/?p=776#comment-1767 <p>Firefox <em>must</em> save that URL. The HTTP spec specifies this behaviour on a 302 redirect, because a 302 means that the resource may move to the original location again later, so you need to cache the 'original' URL.</p> <p>The correct solution is for Google to send a 303</p> Firefox must save that URL. The HTTP spec specifies this behaviour on a 302 redirect, because a 302 means that the resource may move to the original location again later, so you need to cache the ‘original’ URL.

The correct solution is for Google to send a 303

]]>