* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #338 (closed editorial: incorporated)

Opened 3 years ago

Last modified 3 years ago

Content-Location doesn't constrain the cardinality of representations

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 19
Component: p3-payload Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/02549C0B-BB8A-4D5D-A2A0-369C623D7803@mnot.net

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

338.diff (1.1 KB) - added by julian.reschke@gmx.de 3 years ago.
Proposed patch

Change History

Changed 3 years ago by julian.reschke@gmx.de

Proposed patch

comment:1 Changed 3 years ago by julian.reschke@gmx.de

  • Owner changed from draft-ietf-httpbis-p3-payload@tools.ietf.org to julian.reschke@gmx.de

comment:2 Changed 3 years ago by julian.reschke@gmx.de

From [1593]:

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

comment:3 Changed 3 years ago by julian.reschke@gmx.de

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

comment:4 Changed 3 years ago by julian.reschke@gmx.de

From [1594]:

regen -19 draft (see #338)

Note: See TracTickets for help on using tickets.