On Mon, May 09, 2005 at 10:53:14AM -0600, Antone Roundy wrote: > > 302 would result in feed readers (that follow the HTTP spec) continuing > to hit the publisher's site every time they checked the feed, and then > going to FeedBurner.
I'm not sure how user agents would handle it, but one could always attach some caching headers to that 302 response to indicate that the 302 is semi-permanent. In theory, user agents could hold on to that 302 response for a little while and follow the "cached" redirection. David -- == David Nesting WL7RO Fastolfe [EMAIL PROTECTED] http://fastolfe.net/ == fastolfe.net/me/pgp-key A054 47B1 6D4C E97A D882 C41F 3065 57D9 832F AB01
