A 200 (OK) response to GET carries a Content-Location value that differs from the target URI. What is the origin server claiming?
That the response is a cached copy retrieved from the named URI
That subsequent requests must be sent to the Content-Location URI instead
That the target URI has moved and the client should update its references
That the target URI is subject to content negotiation and Content-Location is a more specific identifier for the selected representation✓Correct answer
Explanation
Content-Location is representation metadata, not a replacement for the target URI: on a GET or HEAD a differing value points at the specific negotiated variant. Telling a client that a resource has moved is the job of Location on a 3xx response.