For the searching, use querystrings. This is perfectly RESTful: /cars?color=blue&type=sedan&doors=4 An advantage to regular querystrings is that they are standard and widely understood and that they can be generated from form-get.
A Step Back First and foremost, REST describes a URI as a universally unique ID. Far too many people get caught up on the structure of URIs and which URIs are more “restful” than others. This argument is as ludicrous as saying naming someone “Bob” is better than naming him “Joe” – both names get … Read more
400 Bad Request would now seem to be the best HTTP/1.1 status code for your use case. At the time of your question (and my original answer), RFC 7231 was not a thing; at which point I objected to 400 Bad Request because RFC 2616 said (with emphasis mine): The request could not be understood … Read more
I strongly oppose 404 in favour of 204 or 200 with empty data. Or at least one should use a response entity with the 404. The request was received and properly processed – it did trigger application code on the server, thus one cannot really say that it was a client error and thus the … Read more
How token-based authentication works In token-based authentication, the client exchanges hard credentials (such as username and password) for a piece of data called token. For each request, instead of sending the hard credentials, the client will send the token to the server to perform authentication and then authorization. In a few words, an authentication scheme … Read more
You just need to add [FromUri] before parameter, looks like: GetCategories([FromUri] int[] categoryIds) And send request: /Categories?categoryids=1&categoryids=2&categoryids=3
Using the -X flag with whatever HTTP verb you want: curl -X PUT -d arg=val -d arg2=val2 localhost:8080 This example also uses the -d flag to provide arguments with your PUT request.
The HTTP specification (RFC 2616) has a number of recommendations that are applicable. Here is my interpretation: HTTP status code 200 OK for a successful PUT of an update to an existing resource. No response body needed. (Per Section 9.6, 204 No Content is even more appropriate.) HTTP status code 201 Created for a successful … Read more
The best way to implement a RESTful search is to consider the search itself to be a resource. Then you can use the POST verb because you are creating a search. You do not have to literally create something in a database in order to use a POST. For example: Accept: application/json Content-Type: application/json POST … Read more
Use POST. In 2010, using GET was probably an acceptable answer. But today (in 2013), browsers will pre-fetch pages they “think” you will visit next. Here is one of the StackOverflow developers talking about this issue on twitter: I’d like to thank my bank for making log off a GET request, and the Chrome team … Read more