Explain some of the major HTTP requests.

UI Developer - Interview Questions

HTTP Requests	Description
GET	It is sent when we wish to recover data from the server. GET request is the most typically used HTTP request.
HEAD	The HEAD is a reaction that is the same as the GET request but doesn’t possess a message-body in the response. The HEAD request method is beneficial in retrieving meta-data that is documented as per the headers, without transferring the entire content. The method is commonly utilised when testing hypertext links for recent change, accessibility, and validity.
TRACE	TRACE requests are implemented to invoke a remote, application loop-back test along the path to the target resource. The TRACE method lets users to witness whatever message is being received at the other end of the request chain so that they can utilise the data for testing or diagnostic functions.
POST	This request is utilized to transmit data from the user to the server. By submitting web forms, these requests can be made. The POST request is generally utilized to build data in the database. For instance, when we build a new account on any webpage, we make use of the POST request.
PUT	It is identical to POST, but it is utilized to revise the existing data on the server. For instance, when we wish to revamp our complete account on a web page, we utilize the PUT request.
PATCH	It is identical to PUT and is utilized when we wish to revise a certain field of our data. For instance, when we just wish to update our name or any additional information about our account, we can make use of the PATCH request.

HTTP Status codes	Description
HTTP Status Code 301 - Permanent Redirect	Any time one URL needs to be redirected to another permanently, a 301 redirect should be used. A 301 redirect implies that bots and visitors that come on that page will be taken to the new URL. Link equity is also passed to the new URL via a 301 redirect.
HTTP Status Code 302 - Temporary Redirect	302 redirect is just like a 30, where it passes visitors and bots to the new page, but it may not pass along link equity. It is not recommended using 302 redirects for permanent changes.
HTTP Status Code 404 - Not Found	This implies the server did not find the file or page that the browser is requesting. 404s don’t show whether the missing resource or pages are missing temporarily or permanently. You can check what this appears to be on your site by writing in a URL that doesn’t exist. Every site will have some pages that display the 404 status codes.
HTTP Status Code 200 - OK	This is the ideal status code for a properly functioning page.
HTTP Status Code 410 - Gone	A 410 implies the page is no longer available from the server and they have set no forwarding address. Any links you present on your site that are directed to a 410 page are sending visitors and bots to a dead resource.
HTTP Status Code 500 - Internal Server Error	This status code shows a problem with the server and will affect access to your site. Bots and human visitors alike will get lost, and your link equity will go nowhere fast.
HTTP Status Code 503 - Service Unavailable	503 response, shows that the server is unavailable. This could be because of temporarily overloading the server or maintenance of the server.