|
List Info Thread: BugZilla issue 238 (PROPPATCH response format)
[1]
|
||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||
BugZilla issue 238 (PROPPATCH response format) |
|
List Info Thread: BugZilla issue 238 (PROPPATCH response format)
[1]
|
||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||
. Responses to this method MUST NOT be
cached.
NEW:
The response to a PROPPATCH request can be in two
different formats:
should the server reject the request altogether
(because of missing
access rights, failed conditional headers, malformed
request syntax,
etc.), the status SHOULD be non-2xx HTTP status. On
the other hand,
if the server did attempt the property modification,
the response
status SHOULD be 207 Multistatus, using the
'multistatus' response
body format defined below (Section 9.2.1).
This method is idempotent, but not safe (see section
9.1 of
[RFC2616]). Responses to this method MUST NOT be
cached.
Best regards, Julian
</pre></td>
</tr>
<tr>
<td colspan=){kind=link}