Opened 11 years ago

Closed 6 years ago

#22 closed design (fixed)

ETag (and other metadata) in status messages

Reported by: mnot@… Owned by: fielding@…
Priority: normal Milestone: 22
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:

Description

It's not clear what the headers in a response to a PUT apply to; for example, does an ETag apply to that response, or the response that would be returned upon a GET?

The same questions apply in other cases where the response serves as a status message.

Change History (19)

comment:1 Changed 11 years ago by mnot@…

  • Component set to semantics
  • Milestone set to unassigned
  • version set to d00

comment:3 Changed 11 years ago by mnot@…

related to #69

comment:4 Changed 10 years ago by julian.reschke@…

See related discussion about Content-MD5 near <http://www.w3.org/2002/02/mid/49832D33.4040608@gmx.de>.

comment:5 Changed 10 years ago by mnot@…

  • Priority set to blocked
  • Severity set to Active WG Document

Blocked(-ish) on #110

comment:6 Changed 10 years ago by mnot@…

  • Priority changed from blocked to normal

comment:7 Changed 9 years ago by julian.reschke@…

  • Milestone changed from unassigned to 11

I believe that [856] partly address this; needs review.

comment:8 Changed 9 years ago by mnot@…

  • Milestone changed from 11 to unassigned

comment:9 Changed 9 years ago by mnot@…

  • Priority changed from normal to later

comment:10 Changed 8 years ago by mnot@…

Discussion in Prague (second time around):

Need to identify the scope/target of metadata for all headers (not just ETag; this is just the most obvious case) and nominate in header definitions. E.g.,

  • target resource metadata
  • representation metadata (i.e., on the server)
  • payload metadata (i.e., in the message)
  • control data

comment:11 Changed 8 years ago by mnot@…

  • Priority changed from later to normal

comment:12 Changed 7 years ago by fielding@…

See also [1571]. This may be done.

comment:13 Changed 7 years ago by mnot@…

Paris: add definition of "selected representation" to p2; provide enough context (e.g., examples) so that can be understood by non-Roy mortals.

comment:14 Changed 7 years ago by mnot@…

  • Owner set to fielding@…

comment:15 Changed 7 years ago by julian.reschke@…

(should this be added to "Considerations for new header fields")

comment:16 Changed 6 years ago by fielding@…

From [2111]:

ensure that a validator field sent in response to a successful PUT means something useful; addresses #22 (along with [2110])

comment:17 Changed 6 years ago by fielding@…

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

All aspects of this issue have been addressed.

comment:18 Changed 6 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:19 Changed 6 years ago by mnot@…

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