Opened 15 years ago
Closed 14 years ago
#125 closed design (fixed)
Location Content-Location reference request/response mixup
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | Milestone: | 04 | |
Component: | p2-semantics | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Henrik Nordstrom:
The Content-Location reference in p2 10.4 speaks about Content-Location in request context, when it clearly meant response context.
From:
original location of the entity enclosed in the request. It is
To:
original location of the entity enclosed in the response. It is
Change History (6)
comment:1 Changed 15 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 14 years ago by julian.reschke@…
- Resolution fixed deleted
- Status changed from closed to reopened
comment:3 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from reopened to closed
comment:4 Changed 14 years ago by julian.reschke@…
- Resolution fixed deleted
- Status changed from closed to reopened
comment:5 Changed 14 years ago by julian.reschke@…
- Owner changed from julian.reschle@… to julian.reschke@…
- Status changed from reopened to new
comment:6 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Fixed in [300]:
Resolve #125: s/request/response/ in note about Content-Location vs Location (closes #125).