HTTP Request Method & HTTP Response Status Code

HTTP request methods

● GET

– Metode GET meminta representasi dari sumber daya yang

ditentukan. Permintaan menggunakan GET seharusnya hanya

mengambil data.

● HEAD

– Metode HEAD meminta respons yang identik dengan permintaan

GET, tetapi tanpa body respons.

● POST

– Metode POST digunakan untuk mengirimkan entitas ke sumber daya

yang ditentukan, sering menyebabkan perubahan status atau efek

samping pada server.

● PUT

– Metode PUT menggantikan semua representasi saat ini dari sumber

daya target dengan permintaan yang dikirim

HTTP request methods

● DELETE

– Metode DELETE menghapus sumber daya yang ditentukan.

● CONNECT

– Metode CONNECT membentuk terowongan ke server yang

diidentifikasi oleh sumber daya target.

● OPTIONS

– Metode OPTION digunakan untuk menggambarkan opsi komunikasi

untuk sumber daya target.

● TRACE

– Metode TRACE melakukan message tes loop-back di sepanjang jalan

menuju ke sumber daya target.

● PATCH

– Metode PATCH digunakan untuk menerapkan modifikasi

parsial/sebagian ke sumber daya.

HTTP response status codes

1.Informational responses ( 100 – 199 ),

2.Successful responses ( 200 – 299 ),

3.Redirects ( 300 – 399 ),

4.Client errors ( 400 – 499 ),

5.Server errors ( 500 – 599 ).

Information responses

● 100 Continue

– This interim response indicates that everything so far is OK and

that the client should continue the request, or ignore the

response if the request is already finished.

● 101 Switching Protocol

– This code is sent in response to an Upgrade request header from

the client, and indicates the protocol the server is switching to.

● 103 Early Hints

– This status code is primarily intended to be used with the Link

header, letting the user agent start preloading resources while the

server prepares a response.

Successful responses (1)

● 200 OK

– The request has succeeded. The meaning of the

success depends on the HTTP method:

● GET : The resource has been fetched and is transmitted

in the message body.

● HEAD : The entity headers are in the message body.

● PUT or POST : The resource describing the result of the

action is transmitted in the message body.

● TRACE : The message body contains the request

message as received by the server

Successful responses (2)

● 201 Created

– The request has succeeded and a new resource has been

created as a result. This is typically the response sent after

POST requests, or some PUT requests.

● 202 Accepted

– The request has been received but not yet acted upon. It is

noncommittal, since there is no way in HTTP to later send an

asynchronous response indicating the outcome of the

request.

– It is intended for cases where another process or server

handles the request, or for batch processing.

Successful responses (3)

● Lihat daftar kode selanjutnya di materi PDF..

Redirection messages (1)

● 300 Multiple Choice

– The request has more than one possible response. The user[1]agent or user should choose one of them. (There is no

standardized way of choosing one of the responses, but HTML

links to the possibilities are recommended so the user can

pick.)

● 301 Moved Permanently

– The URL of the requested resource has been changed

permanently. The new URL is given in the response.

● 302 Found

– This response code means that the URI of requested resource

has been changed temporarily. Further changes in the URI

might be made in the future. Therefore, this same URI should

be used by the client in future requests.

Redirection messages (2)

● 303 See Other

– The server sent this response to direct the client to get the requested

resource at another URI with a GET request.

● 304 Not Modified

– This is used for caching purposes. It tells the client that the response

has not been modified, so the client can continue to use the same

cached version of the response.

● 305 Use Proxy

– Defined in a previous version of the HTTP specification to indicate that a

requested response must be accessed by a proxy. It has been

deprecated due to security concerns regarding in-band configuration of

a proxy.

● 306 unused

– This response code is no longer used; it is just reserved. It was used in

a previous version of the HTTP/1.1 specification

Client error responses (1)

● 400 Bad Request

– The server could not understand the request due to invalid syntax.

● 401 Unauthorized

– Although the HTTP standard specifies "unauthorized", semantically

this response means "unauthenticated". That is, the client must

authenticate itself to get the requested response.

● 402 Payment Required

– This response code is reserved for future use. The initial aim for

creating this code was using it for digital payment systems, however

this status code is used very rarely and no standard convention exists.

● 403 Forbidden

– The client does not have access rights to the content; that is, it is

unauthorized, so the server is refusing to give the requested resource.

Unlike 401, the client's identity is known to the server.

Client error responses (2)

● 404 Not Found

– The server can not find the requested resource. In the browser, this means

the URL is not recognized. In an API, this can also mean that the endpoint

is valid but the resource itself does not exist. Servers may also send this

response instead of 403 to hide the existence of a resource from an

unauthorized client. This response code is probably the most famous one

due to its frequent occurrence on the web.

● 405 Method Not Allowed

– The request method is known by the server but has been disabled and

cannot be used. For example, an API may forbid DELETE-ing a resource.

The two mandatory methods, GET and HEAD , must never be disabled and

should not return this error code.

● 406 Not Acceptable

– This response is sent when the web server, after performing server-driven

content negotiation, doesn't find any content that conforms to the criteria

given by the user agent.

Server error responses (1)

● 500 Internal Server Error

– The server has encountered a situation it doesn't know

how to handle.

● 501 Not Implemented

– The request method is not supported by the server and

cannot be handled. The only methods that servers are

required to support (and therefore that must not return

this code) are GET and HEAD .

● 502 Bad Gateway

– This error response means that the server, while working

as a gateway to get a response needed to handle the

request, got an invalid response.

Server error responses (2)

● 503 Service Unavailable

– The server is not ready to handle the request. Common causes are a

server that is down formaintenance or that is overloaded. Note that

together with this response, a user-friendly page explaining the

problem should be sent. This responses should be used for temporary

conditions and the Retry-After: HTTP header should, if possible,

contain the estimated time before the recovery of the service. The

webmaster must also take care about the caching-related headers that

are sent along with this response, as these temporary condition

responses should usually not be cached.

● 504 Gateway Timeout

– This error response is given when the server is acting as a gateway

and cannot get a response in time.

● 505 HTTP Version Not Supported

– The HTTP version used in the request is not supported by the server

Dedy Priyanto

Freelancer

Bagikan Artikel ini