Mail sent on the 08/22 and apparently lost. -- Hello Vincent,
this question comes back now and then (see [1] and [2]). The current conclusion is that, as some other implementations, it has been decided to forbid empty entities for PUT requests inside Restlet according to a strict interpretation of the HTTP spec. Since the POST method has a more general meaning, empty entities are tolerable which explains the difference. Having said that, and since internet browsers don't support PUT requests, Restlet should provide ways to generate PUT-like requests. A step has been accomplished with the TunnelFilter (see [3] and [4]) which allows to fake a PUT with a POST. If you can't use POST but only GET requests, you seem to have a need that is not satisfied yet. You can achieve it with an additionnal filter that checks the query string and sets the entity of the PUT request. I've entered an RFE (http://restlet.tigris.org/issues/show_bug.cgi?id=575) for this point. I end with the fact that there is a huge drawback: it breaks the semantics of GET requests which is used for retrieval. Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org <http://www.restlet.org/> Noelios Technologies ~ Co-founder ~ http://www.noelios.com <http://www.noelios.com/> [1] http://restlet.tigris.org/servlets/ReadMsg?list=discuss&&msgNo=3903 [2] http://restlet.tigris.org/servlets/ReadMsg?listName=discuss&msgNo=5298 [3] http://www.restlet.org/documentation/1.1/faq#19 [4] http://www.restlet.org/documentation/1.1/api/org/restlet/service/TunnelService.html
Hi, My application use the PUT methods to update some business objects, but some of these PUT methods do not expect an entity (the value is a string passed in the query string). RESTlet returns an HTTP 400 status. Is it a strict behavior required by the RFC? I expected the same behavior as the handlePost() method: a log trace, then a call to storeRepresentation with a 'null' param. So, is it a bug of an HTTP "feature"? Regards,
