Selection based upon request target

[mnot]

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."

Reported by @mnot, migrated from https://trac.ietf.org/trac/httpbis/ticket/488

[mnot]

@mnot changed summary from Selection basis upon request target to Selection based upon request target

[mnot]

julian.reschke@gmx.de commented:

Maybe "target resource"?

[mnot]

@mnot commented:

Hmm, it really is the identifier, not the resource, that is "part of the request message."

[mnot]

julian.reschke@gmx.de commented:

The same applies to the effective request URI...

[mnot]

@mnot commented:

Well, yes, but it's a concrete artefact that can be derived from the request message; a target resource is an ephemeral concept...

[mnot]

julian.reschke@gmx.de commented:

Maybe "the parts used to select the target resource"? (for the effective request URI, we also consider protocol and host header field)

[mnot]

@mnot commented:

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...

[mnot]

julian.reschke@gmx.de commented:

From 2294:

tune "Vary" description (see #488)

[mnot]

• julian.reschke@gmx.de changed milestone from unassigned to 23
• julian.reschke@gmx.de changed resolution to incorporated
• julian.reschke@gmx.de changed status from new to closed

[mnot]

fielding@gbiv.com commented:

From 2324:

Fix a missing comma and clarify that Vary in a response is about this response; updates 2294 which addresses #488