Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#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)

338.diff (1.1 KB) - added by julian.reschke@… 6 years ago.
Proposed patch

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by julian.reschke@…

Proposed patch

comment:1 Changed 6 years ago by julian.reschke@…

  • Owner changed from draft-ietf-httpbis-p3-payload@… to julian.reschke@…

comment:2 Changed 6 years ago by julian.reschke@…

From [1593]:

Content-Location doesn't constrain the cardinality of representations (see #338)

comment:3 Changed 6 years ago by julian.reschke@…

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

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

From [1594]:

regen -19 draft (see #338)

Note: See TracTickets for help on using tickets.