REST just says that you should conform to the uniform interface. In other words, it says you should do what POST is supposed to do as per the HTTP spec. Here is the quote from that spec that is relevant, If a resource has been created on the origin server, the response SHOULD be 201 … Read more
It’s actually not really clearly stated in the standard (RFC 3986) whether a percent-encoded version of . or .. is supposed to have the same this-folder/up-a-folder meaning as the unescaped version. Section 3.3 only talks about “The path segments . and ..”, without clarifying whether they match . and .. before or after pct-encoding. Personally … Read more
As per request, a simple REST-like approach. It works almost the same way Codemwncis’ solution works but uses the Accept header for content negotiation. First the routes file: GET /user/{id} Application.user POST /user/ Application.createUser PUT /user/{id} Application.updateUser DELETE /user/{id} Application.deleteUser You don’t specify any content type here. Doing so is IMHO only necessary when you … Read more