- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 09 Jul 2009 12:48:18 +0200
- To: "Roy T. Fielding" <fielding@gbiv.com>
- CC: Jonathan Rees <jar@creativecommons.org>, Pat Hayes <phayes@ihmc.us>, HTTP Working Group <ietf-http-wg@w3.org>, www-tag@w3.org
Roy T. Fielding wrote: > ... > That's because you happen to be reading it differently than > what I was thinking when I wrote it. The sentence is a bit > ambiguous if you don't pay attention to what the second "that" > means. If it is reordered to say > > A 303 response to a GET request indicates that the server does > not have a transferable representation of the requested resource > and is instead redirecting the client to some other resource > for further information. > > then I think the objection is handled without watering down > the purpose of using the status code on a GET. > > ....Roy Sounds good to me. BR, Julian
Received on Thursday, 9 July 2009 10:49:01 UTC