![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
#501 closed editorial (incorporated)
idempotency: clarify "effect"
| Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p2-semantics@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 25 |
| Component: | p2-semantics | Severity: | In WG Last Call |
| Keywords: | Cc: |
Description
Gili:
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 (3)
comment:1 Changed 9 years ago by julian.reschke@…
comment:2 Changed 9 years ago by julian.reschke@…
- Milestone changed from unassigned to 25
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 9 years ago by fielding@…
Note: See
TracTickets for help on using
tickets.
From [2427]:
Clarify that idempotency is about effects on the server, and mention that response messages may vary for repeated requests (see #501)