#488 closed editorial (incorporated)
Selection based upon request target
Reported by: | mnot@… | Owned by: | draft-ietf-httpbis-p2-semantics@… |
---|---|---|---|
Priority: | normal | Milestone: | 23 |
Component: | p2-semantics | Severity: | In WG Last Call |
Keywords: | Cc: |
Description
https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p2-semantics.html#header.vary says:
The "Vary" header field describes what parts of a request message, aside from the method and request target, might influence the origin server's process for selecting and representing the response. The value consists of either a single asterisk ("*") or a list of header field names (case-insensitive).
"request target" isn't appropriate here; use "effective request URI."
Change History (10)
comment:1 Changed 9 years ago by mnot@…
- Summary changed from Selection basis upon request target to Selection based upon request target
comment:2 Changed 9 years ago by julian.reschke@…
comment:3 Changed 9 years ago by mnot@…
Hmm, it really is the identifier, not the resource, that is "part of the request message."
comment:4 Changed 9 years ago by julian.reschke@…
The same applies to the effective request URI...
comment:5 Changed 9 years ago by mnot@…
Well, yes, but it's a concrete artefact that can be derived from the request message; a target resource is an ephemeral concept...
comment:6 Changed 9 years ago by julian.reschke@…
Maybe "the parts used to select the target resource"? (for the effective request URI, we also consider protocol and host header field)
comment:7 Changed 9 years ago by mnot@…
The "Vary" header field describes what parts of a request message, aside from the method, the Host header field and the request target, might influence...
comment:8 Changed 9 years ago by julian.reschke@…
comment:9 Changed 9 years ago by julian.reschke@…
- Milestone changed from unassigned to 23
- Resolution set to incorporated
- Status changed from new to closed
Maybe "target resource"?