Re: PUT and DELETE methods in 200 code

On 04.04.2011 19:49, Cameron Heavon-Jones wrote:
> ...
> Doesn't this leave the default behaviour of services to be browser-sniffing again? If no decision can be made based on Accept, there is no other information from which to deduce the content to produce, if any. That a user requires the information is only deducible by the UA.

Well, we should do better than browser sniffing.

> The alternative is to mandate that content is provided for all responses (even if that content is empty), and for the server to pick the most relevant format by means of Accept.

The hard part is not whether or not to send content, but *what* to send. 
Some clients may want a new representation of the resource (PUT->200), 
some will not.

>...

BR, Julian

Received on Monday, 4 April 2011 17:58:17 UTC