> On Wed, Aug 28, 2002 at 02:03:58PM +0200, Stefan Eissing wrote: > > 301 is a bad choice since this indicates that "... the requested > > resource has been assigned a new permanent uri..." (RFC > 2616). But the > > "neaerest gas station" resource is still at > > http://example.org/nearest/gas/. It just "points" to a another > > resource which is the nearest one according to "context" > information. > > So 302 would be better, but not ideal either. > > My bad. After all these years, I still get 301 and 302 confused. 8-( And PHP and most HTML/Web app developers confuse 302 and 303. (They send '302 Moved Temporarily' when it should be '303 See Also' - backward compatibility I suppose).Received on Wednesday, 28 August 2002 12:11:39 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:55:42 GMT