Opened 12 years ago
Closed 10 years ago
#209 closed editorial (fixed)
identified resource indepent of scheme?
Reported by: | julian.reschke@… | Owned by: | fielding@… |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
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 (5)
comment:1 Changed 12 years ago by mnot@…
- Type changed from design to editorial
comment:2 Changed 10 years ago by julian.reschke@…
Thread continued at <http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0032.html>
comment:3 Changed 10 years ago by mnot@…
- Severity changed from Candidate WG Document to Active WG Document
comment:4 Changed 10 years ago by mnot@…
- Owner set to fielding@…
comment:5 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from new to closed
Closing; PUT's definition no longer refers to request-target.
Flipping to Editorial; clearly this is just an artefact of the confusion around request-target, etc.