Personally, both ways are acceptable…. however, if I were you, I’ll opt for option A (check read-only fields to ensure they are not changed, else throw an error). Depending on the scope of your project, you cannot assume what the consumers know about your Restful WS in depth because most of them don’t read documentations … Read more
Ignoring the comment about the REST style mapping CRUD to the HTTP methods, this is an excellent question. The answer to your question is, yes you are free to use PUT in this scenario even though there are some elements of the resource that are updated by the server in a non-idempotent manner. Unfortunately, the … Read more
I asked this question on the Http-WG. This was the most precise answer I got http://lists.w3.org/Archives/Public/ietf-http-wg/2010JulSep/0276.html In summary, POST does not require a body. I would expect the same justification can be applied to PUT.
First of all, you are using an obsolete document: The RFC 2616 is no longer relevant nowadays and anyone using such document as reference should stop right away. Quoting Mark Nottingham who, at the time of writing, co-chairs the IETF HTTP and QUIC Working Groups: Don’t use RFC2616. Delete it from your hard drives, bookmarks, … Read more
The only advantage of POST-creation over PUT-creation is the server generation of IDs. I don’t think it worths the lack of idempotency (and then the need for removing duplicates or empty objets). Instead, I would use a PUT with a UUID in the URL. Owing to UUID generators you are nearly sure that the ID … Read more
Browsers do support PUT and DELETE, but it’s HTML that doesn’t. For example, a browser will initiate a PUT request via Javascript (AJAX), but not via HTML <form> submission. This is because HTML 4.01 and the final W3C HTML 5.0 spec both say that the only HTTP methods that their form elements should allow are … Read more
The difference is that a PUT is for a known resource, and therefor used for updating, as stated here in rfc2616. The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity. That … Read more
I solved the problem with this: ServicePointManager.ServerCertificateValidationCallback = new RemoteCertificateValidationCallback ( delegate { return true; } );
I’ve used a variety of python HTTP libs in the past, and I’ve settled on requests as my favourite. Existing libs had pretty useable interfaces, but code can end up being a few lines too long for simple operations. A basic PUT in requests looks like: payload = {‘username’: ‘bob’, ’email’: ‘bob@bob.com’} >>> r = … Read more