Put happens to be idempotent, in contrast to post. The difference between post and put is that put is idempotent, that means, calling the same put request multiple times will always produce the same result (that is no side effect), while on the other hand, calling a post request repeatedly may have (additional) side effects of creating the same resource multiple times. Can i use a put method in an html form to send data from the form to a server? How do i test a restful put (or delete) method using curl? I was wondering what people's opinions are of a restful put operation that returns nothing (null) in the response body. Since put requests include the entire entity, if you issue the same request repeatedly, it should always have the same outcome (the data you sent is now the entire data of the entity)
Using put wrong what happens if you use the above patch data in a put request? I'm building a restful api using zend framework via the zend_rest_route For uploading of files, should i use put or post to handle the process I'm trying to be as consistent as possible with the But what is the definition of 'enclosed entity'? I have few questions that
Should i use patch in case of verify (or anyother action where just recordid and versionno send to server to change some fields) or it is ok to use put.
OPEN
