Opened 10 years ago

Closed 9 years ago

Last modified 8 years ago

#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)

i196.2.diff​ (6.1 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2
i196.diff​ (6.3 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2
i196.3.diff​ (6.9 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2
i196.4.diff​ (6.8 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2
i196.5.diff​ (18.1 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2
i196.6.diff​ (21.3 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for Part 2 and 6
i196.7.diff​ (28.0 KB) - added by julian.reschke@… 9 years ago.
Proposed def of "effective request URI", including questions, plus patches for the other parts.

Download all attachments as: .zip

Change History (21)

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

From [694]:

note "Request-URI" issue number in comment (see #196)

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

From [695]:

Clarify rules for determining what entities a response carries (see #110 #196)

comment:3 Changed 10 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 10 years ago by mnot@…

  • Type changed from design to editorial

comment:6 Changed 9 years ago by mnot@…

  • Priority changed from normal to urgent

comment:7 Changed 9 years ago by julian.reschke@…

  • Milestone changed from unassigned to 10

comment:8 Changed 9 years ago by julian.reschke@…

From [809]:

add paragraph break for clarity (related to #196)

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for Part 2 and 6

Changed 9 years ago by julian.reschke@…

Proposed def of "effective request URI", including questions, plus patches for the other parts.

comment:9 Changed 9 years ago by julian.reschke@…

From [823]:

Introduce term "effective request URI" and use it throughout; may require some more fine-tuning (see #196)

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

  • Milestone changed from 10 to 11

(this is work in progress)

comment:11 Changed 9 years ago by julian.reschke@…

  • Milestone changed from 11 to 10
  • Resolution set to incorporated
  • Status changed from new to closed

remaining questions raised as #221 and #222.

comment:12 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:13 Changed 9 years ago by mnot@…

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

comment:14 Changed 8 years ago by julian.reschke@…

From [1340]:

fix example for * in effective request URI (related to #196)

Note: See TracTickets for help on using tickets.