Hi Vincent, We had this discussion a few month ago: http://thread.gmane.org/gmane.comp.web.services.rest/8046
In short, the conclusion was that a PUT without an entity wasn't allowed, but a PUT with a "Content-Length: 0" entity was.
Strictly speaking, the query string in the URI is part of the URI. Thus, every time you change this query string, you effectively make a request to a different resource potentially. Perhaps the problem you're having is a symptom showing that these parameters ought to be in the body of the request.
Best wishes, Bruno. Vincent Ricard wrote:
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,
