πΉ GET
πΉ PUT
πΉ POST
πΉ HEAD
πΉ TRACE
πΉ PATCH
πΉ DELETE
πΉ OPTIONS
πΉ CONNECT
Let's talk about them in a bit more detail π§΅ππ»
HTTP request methods are the actions initiated from the client-side to perform certain actions.
These HTTP request methods are sometimes called nouns or referred to as HTTP verbs.
π GET
The GET method is the most common of all these request methods. It is used to get the desired resources from the server.
The GET methods don't affect the state of the server.
π POST
The POST method is used to submit the information to the server. As we're submitting data, the POST method often changes the state of the server.
π PUT
The PUT method is used whenever you need to change the resource. The resource, which is already a part of resource collection.
π PATCH
The PATCH request method is used to modify only the necessary part of the data or response. The PATCH method doesn't modify the entire response.
π HEAD
The server sends the response without the body. The HEAD method asks for a response identical to that of a GET request, but it is faster as small data is transferred.
π DELETE
As the name says, the DELETE request method is used to delete the specified resource. It requests that the origin server delete the resource identified by the Request-URL.
π CONNECT
The CONNECT method establishes two-way communication between the client and the requested resource.
CONNECT request method is used to push your proxy to start an HTTP tunnel.
π OPTIONS
The OPTIONS method is used to describe the communication options available for the target resource. The client can either specify a URL for describing the communication options available for a specific resource or an asterisk (*) if they want to target the server.
π TRACE
The TRACE method is generally used for debugging. It performs a message loop-back test along the path to the desired data.
We will post a sequel thread covering the three main characteristics of an HTTP request method.
1. Safe 2. Idempotent 3. Cacheable
Sounds good? Stay in touch with @Rapid_API ππ
It's out!
Give it a read to this thread if you want to learn more about HTTP request methods. We have covered some important points here. π
- This API provides sentiment analysis, stemming and lemmatization, part-of-speech tagging and chunking, phrase extraction, and named entity recognition.
API testing is performed to test whether a particular API meets some pre-defined parameters or not.
Let's talk more about API Testing π§΅ππ»
API testing includes testing APIs in isolation to ascertain if they meet the functionality, reliability, latency, performance, security, and other essential parameters.
API testing commonly includes testing APIs with JSON or XML payload sent over HTTP, HTTPS, JMS, and MQ. These are widely used data formats and networking/messaging protocols.
Let's try to know more about Pub/Sub design pattern and learn some facts about it.
π§΅ππ»
Publish/Subscribe (Pub/Sub) is an asynchronous messaging style used in serverless and microservices architectures.
With this model, messages are not sent to a specific subscriber but are instead categorized to be available to all subscribers of the category.
π How Pub/Sub Pattern Based APIs Work
The main characteristic of Pub/Sub APIs is the existence of publishers and subscribers, as the name implies. Publishers categorize messages and those that are subscribed to a specified category receive that message.
There are three main characteristics of HTTP Request Methods:
1. Safe 2. Idempotent 3. Cacheable
Let's talk about them in this thread. π§΅ππ»
πΈ Safe
We can call an HTTP request method safe if it doesn't affect the server's state.
The safe methods request the server to send data without performing any modification to the original data. Hence safe methods accomplish read-only operations.
Even though they are read-only operations, they sometimes cause a change in server state; the server can update its statistics.
One thing to note here is that the safe methods never request the server to change its state.