Re: Re: Put with no content

Hello, Restlet now complains that the content length must be greater than or equal to zero. As pointed out by other posters, this is an artificial constraint imposed by Restlet. In many cases, the URI itself carries sufficient information. If I have a look at the HTTP specifications (

RE: Re: Re: Put with no content

Thanks Thierry :-) -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3085213

RE: Re: Put with no content

I tried setting the content length to -1, as per MSDN: The ContentLength property contains the value of the Content-Length header returned with the response. If the Content-Length header is not set in the response, ContentLength is set to the value -1. Restlet now complains that the content

RE: Re: Put with no content

Follow-up: It *does* get through if I can arrange to not set the content length at all. However, this requires some deviousness on the client side. I would personally much prefer if Restlet ignored a content length of zero. --

RE: Re: Put with no content

Thanks Thierry. I believe it happens specifically when the content length is set to zero (from my reading of previous posts on the subject, and from my own specific case). I have declared simply: @Put public void update(); The 'update' method is never called. I.e., the client gets the