RE: succeed code for DELETE

Hi Geoff,
Yes, I meant 2518..that was a typo.
 
At the end of section 8.6 (DELETE), there is a statement which states that 204 should not be included in a 207. 
"The reason for this prohibition is that 204 (No Content) is the default success code."
It was this particular phrase which confused me.

Regards,
Girish


________________________________

	From: ietf-dav-versioning-request@w3.org [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Geoffrey M Clemm
	Sent: Tuesday, September 14, 2004 7:09 PM
	To: 'ietf-dav-versioning@w3.org'
	Subject: Re: succeed code for DELETE
	
	

	I assume you meant "2518", not "2158". 
	
	What in 2518 made you think 204 was the "default" success code 
	for DELETE?  In particular, the definition of DELETE in 2518 
	(which is a copy of the definition from 2616) states: 
	
	"A successful response SHOULD be 200 (OK) if the response includes 
	an entity describing the status, 202 (Accepted) 
	if the action has not yet been enacted, or 204 (No Content) 
	if the action has been enacted but the response does not 
	include an entity." 
	
	So you would use 200 or 202 if you wanted to include a body. 
	
	Cheers, 
	Geoff 
	
	
	Girish wrote on 09/14/2004 10:42:32 AM:
	
	> 
	> Hi,
	> Can a successful DELETE (in my case, deletion of a version-history) 
	> return some content (some href, for example) to the client? 
	> RFC 2158 states that 204 (no content) is the default success code 
	> for DELETE.  I was wondering if there are special deltaV semantics.
	> 
	> Thanks,
	> Girish
	>

Received on Wednesday, 15 September 2004 06:59:39 UTC