A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn’t follow the rules. In the case of a REST API with a JSON payload, 400’s are typically, and correctly I would say, used to indicate that the JSON is invalid in some way … Read more
Best practice for RESTful API design is that path params are used to identify a specific resource or resources, while query parameters are used to sort/filter those resources. Here’s an example. Suppose you are implementing RESTful API endpoints for an entity called Car. You would structure your endpoints like this: GET /cars GET /cars/:id POST … Read more
I’ve tried both design strategies – nested and non-nested endpoints. I’ve found that: if the nested resource has a primary key and you don’t have its parent primary key, the nested structure requires you to get it, even though the system doesn’t actually require it. nested endpoints typically require redundant endpoints. In other words, you … Read more
This worked for me: curl -v –cookie “USER_TOKEN=Yes” http://127.0.0.1:5000/ I could see the value in backend using print(request.cookies)
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
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 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