What exactly is the HTTP-based system.
Thread ๐งต๐๐ป
Thread ๐งต๐๐ป
HTTP is a communication protocol that establishes the connection between web browsers and web servers.
HTTP is entirely based on the client-server model, where the client initiates the request then waits until it receives a response from the server.
Typically, there are 3 main components in the HTTP-based system. ๐๐ป
The client can initiate the request using HTTP request methods.
๐ HTTP request methods are the actions initiated from the client-side to get the desired resource.
๐ HTTP request methods are the actions initiated from the client-side to get the desired resource.
There are 9 HTTP request methods:
- GET
- PUT
- POST
- HEAD
- TRACE
- PATCH
- DELETE
- OPTIONS
- CONNECT
- GET
- PUT
- POST
- HEAD
- TRACE
- PATCH
- DELETE
- OPTIONS
- CONNECT
But there are four widely used HTTP verbs:
๐ GET (read existing data)
๐ฒ POST (create a new response or data)
โป๏ธ PATCH (update the data)
๐๏ธ DELETE (delete the data)
๐ GET (read existing data)
๐ฒ POST (create a new response or data)
โป๏ธ PATCH (update the data)
๐๏ธ DELETE (delete the data)
Check out this thread for a detailed explanation of each and every HTTP verb.
There are three main characteristics of HTTP Request Methods:
1. Safe
2. Idempotent
3. Cacheable
1. Safe
2. Idempotent
3. Cacheable
๐ 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.
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.
๐ Idempotent
Idempotent methods have no side effects on the server. We can call them in a row, and they guarantee that they will not affect the server state (except for keeping statistics).
GET, HEAD, OPTIONS, PUT, DELETE, and TRACE methods are idempotent.
Idempotent methods have no side effects on the server. We can call them in a row, and they guarantee that they will not affect the server state (except for keeping statistics).
GET, HEAD, OPTIONS, PUT, DELETE, and TRACE methods are idempotent.
๐ Cacheable
As the term suggests, we can call HTTP response methods cacheable if it is possible to cache the response for later use.
As the term suggests, we can call HTTP response methods cacheable if it is possible to cache the response for later use.
Moving forward, what if the client or server wants to send an extra bit of information through request or respectively?
Here HTTP headers come into play. ๐๐ป
Here HTTP headers come into play. ๐๐ป
The HTTP headers are divided into four categories:
1๏ธโฃ Request headers: Client to Server
2๏ธโฃ Response headers: Server to Client
3๏ธโฃ Representation headers: Information about the body of the resource
4๏ธโฃ Payload headers: Information about the payload data
1๏ธโฃ Request headers: Client to Server
2๏ธโฃ Response headers: Server to Client
3๏ธโฃ Representation headers: Information about the body of the resource
4๏ธโฃ Payload headers: Information about the payload data
We have a well-written thread on HTTP headers. Please give it a read. ๐๐ป
The next thing we have is HTTP response status codes.
๐น Informational (100โ199)
๐น Successful (200โ299)
๐น Redirects (300โ399)
๐น Client errors (400โ499)
๐น Server errors (500โ599)
๐น Informational (100โ199)
๐น Successful (200โ299)
๐น Redirects (300โ399)
๐น Client errors (400โ499)
๐น Server errors (500โ599)
Server Error Responses (5xx) ๐๐ป
In this thread, we have explained all the status codes in detail.
And that's pretty much about it for this thread.
We hope you find this helpful. If so, share it with your connections. ๐
Also, visit RapidAPI Hub(RapidAPI.com) for more than 35,000 excellent APIs.
We hope you find this helpful. If so, share it with your connections. ๐
Also, visit RapidAPI Hub(RapidAPI.com) for more than 35,000 excellent APIs.
Loading suggestions...