Re: PUT with no entity (architecture question)

[jlouvel]

Hi there,

We had several discussions on this topic. Although PUT with an empty
entity isn't a RESTful design practice, Restlet shouldn't enforce it as
the HTTP spec is unclear about it.

Also, we didn't enforce it correctly as the test wasn't working with
chunked encoding or when the size wasn't known in advance. So, I've
removed the test causing the 400 status.

"Empty entity on PUT"
http://restlet.tigris.org/issues/show_bug.cgi?id=803

Note that it doesn't mean we encourage this practice! :)

Best regards,
Jerome Louvel
--
Restlet ~ Founder and Lead developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com



Rob Heittman a écrit :
> Awesome.  I didn't know this effort existed.  I did not see that they
> have already cleared up this point in the drafts, although they did shed
> light on the Status code issue in another thread.
>
> I'll join the list ... this is stuff we should stay abreast of.
>
> - R
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2413705