I re-read the thread and I thought the only conclusion was that the spec is inconclusive :-) It would probably be better for Restlet just to warn instead of error here. Other frameworks also refuse a no-entity PUT (sorry -- no current list, but empirical past evidence) but I don't see a concrete reason that Restlet should be the enforcer of this particular interpretation. Unless there is a technical reason why supporting a no-entity PUT is a challenge.
- R On Tue, Aug 25, 2009 at 12:40 PM, Brian Demers <[email protected]>wrote: > I have a web app that accepts uploaded files. We are using Restlet 1.1.3. > > If I try to upload a file with 0 bytes I get an error message: "Missing > request entity" > > http://www.mail-archive.com/[email protected]/msg03579.html > > I don't agree with the conclusion here. Uploading a 0 byte file should be > acceptable, and in some cases needed for applications. > > When thinking about a PUT containing a message (json, xml, ect) then a PUT > should not be empty, I could agree with that. In the case of file upload, > it represents the entity being empty, not missing. > > > -- > View this message in context: > http://n2.nabble.com/Upload-a-zero-byte-file-tp3511268p3511268.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2387222 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2387224
