• Register
157 points


Okay the answer is PUT method. This method requests that the entity is stored under the request-uri.

What is uri?

URI stands for Uniform Resource Identifier, and it's the official name for those things you see all the time on the Web that begin ' http: ' or ' mailto: ', for example https://kodlogs.com/  which is the URI for the home page of the Kodlogs.

What is request-uri?

The request URI is the uniform resource identifier of the resource to which the request applies.

What does HTTP request method mean?

HTTP request methods define the action to perform through the request. These are also known as verbs and generally used for CRUD operations, i.e., Create, Read, Update & Delete. Moreover, HTTP request methods are case-sensitive and should always be uppercase.

How many HTTP request methods are there?

There are nine methods.

1.      Safe and Idempotent Methods

2.      Options

3.      Get

4.      Head

5.      POST

6.      PUT

7.      DELETE

8.      TRACE

9.      CONNECT

PUT method

The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource, the enclosed entity SHOULD be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create the resource with that URI. If a new resource is created, the origin server MUST inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No Content) response codes SHOULD be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI, an appropriate error response SHOULD be given that reflects the nature of the problem. The recipient of the entity MUST NOT ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and MUST return a 501 (Not Implemented) response in such cases. If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries SHOULD be treated as stale. Responses to this method are not cacheable.