Connected: An Internet Encyclopedia
RFC 1945 - D.1.1 PUT

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1945
Up: D. Additional Features
Up: D.1 Additional Request Methods
Prev: D.1 Additional Request Methods
Next: D.1.2 DELETE

### D.1.1 PUT

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.

The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity as data to be processed. That resource may be a data-accepting process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server should not apply the request to some other resource.

Next: D.1.2 DELETE

Connected: An Internet Encyclopedia
RFC 1945 - D.1.1 PUT