When talking strictly about REST, POST methods are used to create a new resource into the collection of resources. Use POST APIs to create new subordinate resources, e.g., a file is subordinate to a directory containing it or a row is subordinate to a database table.
#Get vs post code
Similarly, if it is determined that the GET request itself is not correctly formed then the server will return the HTTP response code 400 (BAD REQUEST).Įnter fullscreen mode Exit fullscreen mode.In case the resource is NOT found on the server then API must return HTTP response code 404 (NOT FOUND).For any given HTTP GET API, if the resource is found on the server, then it must return HTTP response code 200 (OK) – along with the response body, which is usually either XML or JSON content (due to their platform-independent nature).If the Request-URI refers to a data-producing process, it is the produced data that shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process. Making multiple identical requests must produce the same result every time until another API (POST or PUT) has changed the state of the resource on the server. As GET requests do not change the resource’s state, these are said to be safe methods.Īdditionally, GET APIs should be idempotent. Use GET requests to retrieve resource representation/information only – and not modify it in any way. Now that we know what HTTP is and why it’s used, let’s talk about the different methods we have available to us.
#Get vs post update
This would make the app bloated and slow, would take forever to research and manually add to a database, and would be a headache to update every single day. This weather app wouldn’t have every city and its weather information coded directly into it. The weather app that your user is going to interact with is the client application – it has buttons, a search bar, and displays data like city name, current temperature, AQI, and so on. Let’s say you were building a weather web app, for example. Your entire client application gets downloaded into the browser, and all of the data can be accessed by anyone accessing your web page. The main reason for this separation is to secure sensitive information. A server application is a program that is running somewhere, listening, and waiting for a request. A server application is the one that sends the content, or resource, to your client application. This architecture describes how all web applications work and defines the rules for how they communicate.Ī client application is the one that a user is actually interacting with, that's displaying the content. In order to understand the HTTP methods, it’s important to cover the concept of client/server architecture. It is the mechanism that allows developers to request resources. API stands for application programming interface. These resources are made available to us via an API and we make requests to these APIs via the HTTP protocol. Resources could mean anything from HTML files to data from a database, photos, text, and so on.
HTTP is a protocol, or a definite set of rules, for accessing resources on the web.
0 kommentar(er)
