Opened 12 years ago
Closed 12 years ago
#205 closed editorial (wontfix)
placement of entity tag def
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | non-specific | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Entity tags are currently defined in part 4 (cond), but it appears to me that they really belong into part 3 (payload).
Change History (3)
comment:1 Changed 12 years ago by fielding@…
comment:2 Changed 12 years ago by mnot@…
I actually think the current layout makes the most sense:
- Splitting LM and ETag from the conditional headers is more jarring.
- The dependencies in p6 are minimal (and probably can be reduced).
- Folding all of p4 into p2 isn't really attractive, IMO.
comment:3 Changed 12 years ago by julian.reschke@…
- Resolution set to wontfix
- Status changed from new to closed
I was convinced it's OK the way it is.
Note: See
TracTickets for help on using
tickets.
Not really. Entity tags have more to do with resource mapping to representations on the server than they do with message content. In particular, one cannot edit an entity tag directly.
We might want to move all of part 4 into part 2, if we want to do some merging.