Skip to content
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

Closed
mnot opened this issue Feb 2, 2022 · 8 comments
Closed

Identifying QUERY results #1918

mnot opened this issue Feb 2, 2022 · 8 comments
Assignees

Comments

@mnot
Copy link
Member

mnot commented Feb 2, 2022

It might be good to explicitly point out that QUERY responses don't have a URL to identify them, as per core.

@reschke
Copy link
Contributor

reschke commented Feb 2, 2022

...unless indicated by Content-Location, right?

@mnot
Copy link
Member Author

mnot commented Feb 3, 2022

Yes. Probably with something like:

Note that a response to a QUERY request, is not identified by the target URI; see [ref to core].

@reschke
Copy link
Contributor

reschke commented Feb 3, 2022

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.

@mnot
Copy link
Member Author

mnot commented Feb 6, 2022

Because QUERY will be considered by many as a drop-in replacement for GET, and may not realise this implication.

@mnot mnot self-assigned this Jul 29, 2022
@mnot mnot added editorial and removed editorial labels Jul 29, 2022
@mnot
Copy link
Member Author

mnot commented Feb 1, 2023

See also #1745.

@reschke
Copy link
Contributor

reschke commented Sep 14, 2024

@mnot - given the resolution of #1745 - this can be closed, right?

@mnot
Copy link
Member Author

mnot commented Sep 16, 2024

Think so - need to review but if you think it's addressed go ahead and close.

@reschke
Copy link
Contributor

reschke commented Sep 19, 2024

We believe this has been taken care of with #1745.

@reschke reschke closed this as completed Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants