Opened 11 years ago

Closed 10 years ago

#331 closed editorial (incorporated)

clarify that 201 doesn't require Location header fields

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

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 (2)

331.diff​ (1.4 KB) - added by julian.reschke@… 10 years ago.
Proposed patch
331.2.diff​ (1.7 KB) - added by julian.reschke@… 10 years ago.
Proposed patch

Download all attachments as: .zip

Change History (5)

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

  • Owner changed from draft-ietf-httpbis-p2-semantics@… to julian.reschke@…
  • Status changed from new to assigned

Changed 10 years ago by julian.reschke@…

Proposed patch

Changed 10 years ago by julian.reschke@…

Proposed patch

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

From [1577]:

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

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

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