Contents
Can a PUT request return data?
I think it is possible for the server to return content in response to a PUT. If you are using a response envelop format that allows for sideloaded data (such as the format consumed by ember-data), then you can also include other objects that may have been modified via database triggers, etc.
Does HTTP POST return a response?
Yes you can, and the specification is clear about what you can do and how to do it: The action performed by the POST method might not result in a resource that can be identified by a URI.
How do I know if a post request is successful?
If you pick up the result from when you post you can then check the status code: result = Session. post(SubmitURL, data=PostData) if result. status_code == requests.
Can we use POST instead of get?
GET is used for viewing something, without changing it, while POST is used for changing something. For example, a search page should use GET to get data while a form that changes your password should use POST . Essentially GET is used to retrieve remote data, and POST is used to insert/update remote data.
What should a delete request return?
The short answer is: You should include a response body with an entity describing the deleted item/resource if you return 200. 202 is something like an asynchronous request/response return status.
How can I get my promise result back?
Promise resolve() method: If the value is a promise then promise is returned. If the value has a “then” attached to the promise, then the returned promise will follow that “then” to till the final state. The promise fulfilled with its value will be returned.
What should a POST method return?
The method shall return a set (possibly empty) of object headers for the newly posted object. If a URL has been assigned by the server, then that may be included. Similarly, if a URN has been assigned, then that shall be returned. Other things which may be returned include for example the expiry-date if any.
What’s the best way to return a message?
It’s best to return a message back to the client that represents the exception that happened (with relevant status code). Out of the box you have to use Request.CreateErrorResponse (HttpStatusCode, message) if you want to specify a message.
Is it good practice to send errors back?
At the end of the day it’s an API sending back responses and not views, so I think it’s fine to send back a message with the exception and status code to the consumer. I currently haven’t needed to accumulate errors and send them back as most exceptions are usually due to incorrect parameters or calls etc.
What’s the best way to return a responseentity?
Its possible to return ResponseEntity without using generics, such as follows, Spring 2 introduced ResponseStatusException using this you can return String, different HTTP status code, DTO at the same time. I used to use a class like this.
How to return different types of responseentity in Java?
Each exception handler method will be configured to handle one or more exception types. These methods are where you specify the response type for errors For your example, you would declare (in the controller advice class) an exception handler method for the validation error. The return type would be ResponseEntity