-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content-Location with QUERY #1746
Conversation
So it might be better to be explicit -- if the server wants to create a resource for these results, use |
Given that we're defining this method, it seems like we can specify which is the intended behavior, or provide mechanisms for each. |
Could perhaps a Link: </updated-results>; rel="latest-version", </these-results>; rel="memento" The chosen link relations are probably not appropriate, I just picked some that exists to provide a complete example. |
Per discussion in Brisbane side-meeting:
|
33d548e
to
07e696a
Compare
@@ -200,6 +200,14 @@ q=foo&limit=10&sort=-published | |||
using an HTTP GET request. Various non-normative examples of successful | |||
QUERY responses are illustrated in <xref target="examples" />. | |||
</t> | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review feedback from @reschke.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see nothing here about cacheability or origins. I know that I left early, but I thought that we had concluded that the server claims about the Content-Location resource would be treated differently based on whether the indicated resource was on the same origin (or not).
A successful response to a QUERY request &MAY; include a Content-Location | ||
header field (see <xref target="HTTP" section="8.7"/>) containing an | ||
identifier for a specific resource corresponding to the results of the | ||
operation. A client can send a GET request for the indicated URI to repeat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
operation. A client can send a GET request for the indicated URI to repeat | |
operation. A client can send a GET request for the indicated URI to repeat |
So is this "A client can" or "This represents a claim from the server that a client can"
@martinthomson, I've added language restricting it to same-origin; is there a stronger statement you were expecting to see here? |
Co-authored-by: Julian Reschke <[email protected]>
@mnot , @royfielding , @martinthomson - should we go ahead with this? |
No. See #1745 (comment) |
IETF 120 feedback: define both (the resource that identfies the result of this query), and a resource that can be used with GET to repeat the QUERY itself. |
This looks good (right, @royfielding ?) Looking at the PR, I was going to ask whether Location and Content-Location can be trailers, but found that this is consistent with RFC 9110. Will have a look at the full text later to see how in integrates, and whether we may want to have more examples. |
OK, I think we should add an example to section 4. @MikeBishop - can you move this PR to the WG repo, so I can add to it? |
Fixes #1745.