* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #501 (closed editorial: incorporated)

Opened 18 months ago

Last modified 17 months ago

idempotency: clarify "effect"

Reported by: julian.reschke@gmx.de Owned by: draft-ietf-httpbis-p2-semantics@tools.ietf.org
Priority: normal Milestone: 25
Component: p2-semantics Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/525D7EB2.8020302@bbs.darktech.org



Can the authors officially weigh in on the meaning of "idempotent"

with response to response codes? Do idempotent methods have to return the same response code in the face of multiple invocations? Or are they allowed to return different response codes so long as the state is not modified by subsequent requests? See http://stackoverflow.com/q/741192/14731 for the discussion that fueled this question.

PS: It would be nice if the spec officially clarified this point as

I've seen it brought up again and again in different discussions.

Change History

comment:1 Changed 18 months ago by julian.reschke@gmx.de

From [2427]:

Clarify that idempotency is about effects on the server, and mention that response messages may vary for repeated requests (see #501)

comment:2 Changed 18 months ago by julian.reschke@gmx.de

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

comment:3 Changed 17 months ago by fielding@gbiv.com

From [2481]:

(editorial) slight wording change to [2427] for idempotent methods; see #501

Note: See TracTickets for help on using tickets.