-
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
Identifying QUERY results #1918
Comments
...unless indicated by Content-Location, right? |
Yes. Probably with something like:
|
I'm still confused why we would say that for QUERY, but not for PUT or POST... QUERY is not special with respect to this; GET is. |
Because QUERY will be considered by many as a drop-in replacement for GET, and may not realise this implication. |
See also #1745. |
Think so - need to review but if you think it's addressed go ahead and close. |
We believe this has been taken care of with #1745. |
It might be good to explicitly point out that QUERY responses don't have a URL to identify them, as per core.
The text was updated successfully, but these errors were encountered: