- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 02 Aug 2007 22:51:26 +0200
- To: Yaron Goland <yarong@microsoft.com>
- CC: Stefan Eissing <stefan.eissing@greenbytes.de>, "Roy T.Fielding" <fielding@gbiv.com>, Mark Baker <distobj@acm.org>, Lisa Dusseault <lisa@osafoundation.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Yaron Goland wrote: > I just lived through the issue of returning 'GET Equivalent' content on a method response in Web3S. In the originally released Web3S spec we stated that PUT/POST/UPDATE had to return what this list is discussing as the GET Equivalent content body on the response. But once the OPS folks got a look at that and explained what the bandwidth bills would look like if we did that things got flipped around. Now, by default, we will return 204s on successful responses and define a new header that clients can submit saying "BTW, I'd really like the GET equivalent response." +1. Either do not do it at all (and let clients do the additional GET), or make it "opt in". Best regards, Julian
Received on Thursday, 2 August 2007 20:51:48 UTC