#338 closed editorial (incorporated)
Content-Location doesn't constrain the cardinality of representations
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | 19 |
Component: | p3-payload | Severity: | Active WG Document |
Keywords: | Cc: |
Description
If Content-Location is included in a response message and its value is the same as the effective request URI, then the response payload SHOULD be considered the current representation of that resource.
-->
If Content-Location is included in a response message and its value is the same as the effective request URI, then the response payload SHOULD be considered a current representation of that resource.
Attachments (1)
Change History (5)
Changed 11 years ago by julian.reschke@…
comment:1 Changed 11 years ago by julian.reschke@…
- Owner changed from draft-ietf-httpbis-p3-payload@… to julian.reschke@…
comment:2 Changed 11 years ago by julian.reschke@…
comment:3 Changed 11 years ago by julian.reschke@…
- Milestone changed from unassigned to 19
- Resolution set to incorporated
- Status changed from new to closed
comment:4 Changed 11 years ago by julian.reschke@…
Note: See
TracTickets for help on using
tickets.
Proposed patch