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

Ticket #331 (closed editorial: incorporated)

Opened 3 years ago

Last modified 3 years ago

clarify that 201 doesn't require Location header fields

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 19
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin:

Description

"The newly created resource can be referenced by the URI(s) returned in the payload of the response, with the most specific URI for the resource given by a Location header field."

Some people read this as a requirement to include "Location". At least for PUT->201 that's nonsense, however.

Attachments

331.diff (1.4 KB) - added by julian.reschke@gmx.de 3 years ago.
Proposed patch
331.2.diff (1.7 KB) - added by julian.reschke@gmx.de 3 years ago.
Proposed patch

Change History

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

  • Owner changed from draft-ietf-httpbis-p2-semantics@tools.ietf.org to julian.reschke@gmx.de
  • Status changed from new to assigned

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

Proposed patch

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

Proposed patch

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

From [1577]:

clarify that 201 doesn't require Location header fields (see #331)

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

  • Status changed from assigned to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 19
Note: See TracTickets for help on using tickets.