#196 closed editorial (fixed)
Term for the requested resource's URI
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | urgent | Milestone: | 10 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
We need to come up with a term to denote "the URI that can be inferred from examining the request-target and the Host header."
I think that definition should go into either Part 1, Section 4.1.2 ("request-target") or Section 4.2 ("The Resource Identified by a Request").
request-target allows 4 different formats:
request-target = "*" / absolute-URI / ( path-absolute [ "?" query ] ) / authority
As far as I can tell, Request-URI only needs to be defined for the 2nd and 3rd case.
In case 2 it would be the request-target.
In case 3, it would be "http:" + value of host header + request-target.
But then, what about https? Do we need to consider this in this context? Or should we potentially not include the scheme, thus just use
hier-part [ "?" query ]
? (in which case "Request-URI" would be a bad choice of names).
Attachments (7)
Change History (21)
comment:1 Changed 13 years ago by julian.reschke@…
comment:2 Changed 13 years ago by julian.reschke@…
comment:3 Changed 13 years ago by julian.reschke@…
I believe that "Effective Request URI", as proposed in http://lists.w3.org/Archives/Public/www-archive/2009Sep/att-0051/draft-hodges-strict-transport-sec-05.plain.html, would be a good choice.
comment:4 Changed 13 years ago by mnot@…
- Type changed from design to editorial
comment:5 Changed 13 years ago by julian.reschke@…
comment:6 Changed 13 years ago by mnot@…
- Priority changed from normal to urgent
comment:7 Changed 13 years ago by julian.reschke@…
- Milestone changed from unassigned to 10
comment:8 Changed 13 years ago by julian.reschke@…
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for Part 2 and 6
Changed 13 years ago by julian.reschke@…
Proposed def of "effective request URI", including questions, plus patches for the other parts.
comment:9 Changed 13 years ago by julian.reschke@…
comment:10 Changed 13 years ago by julian.reschke@…
- Milestone changed from 10 to 11
(this is work in progress)
comment:11 Changed 13 years ago by julian.reschke@…
- Milestone changed from 11 to 10
- Resolution set to incorporated
- Status changed from new to closed
comment:12 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:13 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
From [694]:
note "Request-URI" issue number in comment (see #196)