Opened 10 years ago

Closed 9 years ago

#455 closed design (fixed)

PUT + If-Match over-constrained?

Reported by: mnot@… Owned by: draft-ietf-httpbis-p4-conditional@…
Priority: normal Milestone: 24
Component: p4-conditional Severity: In WG Last Call
Keywords: Cc:


I found this old post by Roy at:

"A more interesting question is whether the spec over-constrains the case where a PUT is successful but tried again. In other words, should the server be allowed to accept the PUT if the etag differs but the current state matches what is being PUT? Subversion handles such cases nicely because it is common for two developers to patch the same bugs. I think the "MUST respond with 412" is yet another case of a bogus requirement being added in 2616.

Note: this is an HTTP spec issue, not a REST issue.


HTTPbis still requires 412 when the only thing that differs is etag. Any chance this will change?

Change History (4)

comment:1 Changed 10 years ago by fielding@…

From [2354]:

Allow an origin server to respond with a success status if the precondition is on a state change that already succeeded; also, make the description of If-Unmodified-Since have the same conditions as If-Match; addresses #455

comment:2 Changed 10 years ago by fielding@…

  • Milestone changed from unassigned to 24
  • Resolution set to incorporated
  • Status changed from new to closed

comment:3 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:4 Changed 9 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.