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

Ticket #209 (closed editorial: fixed)

Opened 6 years ago

Last modified 4 years ago

identified resource indepent of scheme?

Reported by: julian.reschke@gmx.de Owned by: fielding@gbiv.com
Priority: normal Milestone: unassigned
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http:///www.w3.org/mid/4BF3F78B.3010506@webr3.org


Raised by Nathan in <http:///www.w3.org/mid/4BF3F78B.3010506@webr3.org>:

The HTTP spec specifies "The PUT method requests that the enclosed entity be stored at the supplied request-target." and under p1 messaging 4.2 "The exact resource identified by an Internet request is determined by examining both the request-target and the Host header field."

The above would lead me to believe that in both an http and https request (when using the 'path-absolute') that the resource identified in both cases is a scheme-less concatenation of host & 'path-absolute'. However when an the request-target is an absolute-URI then..? (do we chop the schemes off to get the resource identified?)"

Change History

comment:1 Changed 5 years ago by mnot@pobox.com

  • Type changed from design to editorial

Flipping to Editorial; clearly this is just an artefact of the confusion around request-target, etc.

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

comment:3 Changed 4 years ago by mnot@pobox.com

  • Severity changed from Candidate WG Document to Active WG Document

comment:4 Changed 4 years ago by mnot@pobox.com

  • Owner set to fielding@gbiv.com

comment:5 Changed 4 years ago by mnot@pobox.com

  • Status changed from new to closed
  • Resolution set to fixed

Closing; PUT's definition no longer refers to request-target.

Note: See TracTickets for help on using tickets.