- From: Julian Reschke <julian.reschke@greenbytes.de>
- Date: Wed, 8 Apr 2020 15:41:35 +0200
- To: RFC Errata System <rfc-editor@rfc-editor.org>, fielding@gbiv.com, superuser@gmail.com, barryleiba@computer.org, mnot@mnot.net, tpauly@apple.com
- Cc: 1983-01-06@gmx.net, ietf-http-wg@w3.org
On 08.04.2020 15:39, RFC Errata System wrote: > The following errata report has been submitted for RFC7232, > "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid6080 > > -------------------------------------- > Type: Technical > Reported by: Michael Osipov <1983-01-06@gmx.net> > > Section: 3.2 > > Original Text > ------------- > If-None-Match can also be used with a value of "*" to prevent an > unsafe request method (e.g., PUT) from inadvertently modifying an > existing representation of the target resource when the client > believes that the resource does not have a current representation > (Section 4.2.1 of [RFC7231]). This is a variation on the "lost > update" problem that might arise if more than one client attempts to > create an initial representation for the target resource. > > Corrected Text > -------------- > > > Notes > ----- > Please clarify what is supposed to happen when If-None-Match is used with unsafe methods and the value is NOT "*". Should the server respond with BAD_REQUEST? > ... This is not an erratum. Please open a ticket at <https://github.com/httpwg/http-core>. Best regards, Julian
Received on Wednesday, 8 April 2020 13:42:03 UTC