-
Notifications
You must be signed in to change notification settings - Fork 4
/
832.txt
54 lines (39 loc) · 2.76 KB
/
832.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
[FIG(quote)[
[FIGCAPTION[
[1] [CITE@en[Complete basic operations using SharePoint 2013 REST endpoints]]
([TIME[2015-07-14 23:19:05 +09:00]] 版)
<https://msdn.microsoft.com/en-us/library/office/jj164022.aspx>
]FIGCAPTION]
> The HTTP request method: GET for read operations and POST for write operations. POST requests can perform update or delete operations by specifying a DELETE, MERGE, or PUT verb in the X-HTTP-Method header.
]FIG]
[FIG(quote)[
[FIGCAPTION[
[2] [CITE@en[Complete basic operations using SharePoint 2013 REST endpoints]]
([TIME[2015-07-14 23:19:22 +09:00]] 版)
<https://msdn.microsoft.com/en-us/library/office/jj164022.aspx>
]FIGCAPTION]
> X-HTTP-Method header
> POST requests for DELETE, MERGE, or PUT operations
> Used to specify that the request performs an update or delete operation. Example: "X-HTTP-Method":"PUT"
]FIG]
[FIG(quote)[
[FIGCAPTION[
[3] [CITE@en[''''''[''''''MS-ODATA'''''']'''''': PATCH/MERGE]]
([TIME[2015-07-14 23:22:58 +09:00]] 版)
<https://msdn.microsoft.com/en-us/library/dd541276.aspx>
]FIGCAPTION]
> The remainder of this section defines a custom HTTP MERGE method that is used in the OData 1.0 and OData 2.0 protocols to specify that an update is to be completed by using merge semantics. All the directives defined for the PUT method in HTTP, as specified in '''['''RFC2616''']''', and AtomPub, as specified in '''['''RFC5023''']''', apply equally to the HTTP MERGE method. The only difference between an HTTP request that uses MERGE or PATCH and PUT is client intent.
> Since MERGE is not one of the verbs that is defined in the HTTP specification '''['''RFC2616''']''', using the MERGE verb may not flow through network intermediaries as seamlessly as methods that are defined in the HTTP specification. The HTTP PATCH verb is preferred over HTTP MERGE when working with data services that support the OData 3.0 protocol. Data services that support the OData 2.0 and OData 3.0 protocols can support verb tunneling to mitigate this limitation, as defined in Tunneled Requests (section 2.2.7.7).
]FIG]
[4] [CITE@en[RFC 3253 - Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)]]
([TIME[2017-09-17 18:19:04 +09:00]])
<https://tools.ietf.org/html/rfc3253#section-11.2>
[5] [CITE@en[RFC 3253 - Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)]]
([TIME[2017-09-17 18:19:04 +09:00]])
<https://tools.ietf.org/html/rfc3253#section-12.14>
[6] [CITE@en[RFC 3253 - Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)]]
([TIME[2017-09-17 18:19:04 +09:00]])
<https://tools.ietf.org/html/rfc3253#section-13.12>
[7] [CITE@en[RFC 3253 - Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)]]
([TIME[2017-09-17 18:19:04 +09:00]])
<https://tools.ietf.org/html/rfc3253#section-14.11>