Content-Type: Content-Type: Content-Location:
Content-*:
Content-Range:
Last-Modified:
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
shouldSHOULD 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.
PUT 方式は、囲まれたRequest-URI が既存の資源を指しておらず、
その URI に要求している利用者エージェントによって新しい資源を定義する能力があるなら、
起源サーバーはその URI に資源を作ることが出来ます。 新しい資源が作られたら、起源サーバーは Request-URI で資源を作るか修正するかできなかったときは、問題の性質を反映して適切な誤り応答を与えるべきです。実体の受信者は、その理解・実装しない Content-* 頭 (例えば
If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries
shouldSHOULD be treated as stale. Responses to this method are not cacheable.
要求がRequest-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
{1945} as data to be processed. That resource{1945,2068} may{2616} might 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{1945} should notMUST NOT attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI, it MUST send a 301 (Moved Permanently) response; the user agent MAY then make its own decision regarding whether or not to redirect the request.
PUT 要求の本質的な違いは、
Request-URI の違った意味を反映しています。
POST 要求の URI は囲まれた実体を処理されるデータとして取扱うPUT 要求の URI は要求に囲まれた実体のを識別します。
利用者エージェントはどの URI が意図されているかを知っており、
サーバーはその要求を他の資源に適用しようと試みてはなりません。サーバーが要求を異なる URI に適用することを望む時は、
A single resource MAY be identified by many different URIs. For example, an article
maymight have a URI for identifying "the current version" which is separate from the URI identifying each particular version. In this case, a PUT request on a general URImaymight result in several other URIs being defined by the origin server.
一つの資源は多くの違った URI で識別して構いません。
例えば、ある記事は特定の版を識別する URI とは別に「現行版」
を識別する URI を持つかもしれません。
この場合、一般 URI への PUT 要求は、結果その起源サーバーが定義する幾つかの他の URI
となるかもしれません。
HTTP/1.1 does not define how a PUT method affects the state of an origin server.
HTTP/1.1 は起源サーバーの状態に PUT 方式がどう影響するかを定義しません。
PUT requests
mustMUST obey the message transmission requirements set out in section 8.2.
PUT 要求は8.2節のメッセージ転送要件に従わなければなりません。
Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request SHOULD be applied to the resource created or modified by the PUT.
特定の実体頭で特に指定されていない限り、
PUT 要求の実体頭は PUT
で作成または修正された資源に適用するべきです。
Example setting "y" to 5 in the matching document without affecting other fields (using jQuery):
$.ajax( { url: "https://api.mongolab.com/api/1/databases/my-db/collections/my-coll/4e7315a65e4ce91f885b7dde?apiKey=myAPIKey",
data: JSON.stringify( { "$set" : { "y" : 5 } } ),
type: "PUT",
contentType: "application/json" } );