Mark Nottingham
Mark Nottingham
As per above, marking as editorial.
On the server side, if a conditional QUERY is received, is evaluating to `true` indicating that the previous QUERY results are still valid for _that_ QUERY, or that they are...
Since ETags are unique (within the scope of representations of the resource in question), as long as the client submits an INM that contains only ETags that it previously received...
So, I think the proposal here is to replace > A conditional QUERY requests that the query be performed only under the circumstances described by the conditional header field(s). with...
It is authored in XML, yes.
My .02 is that a specific usage scenario would need to specify what to do; we shouldn't (and perhaps even can't) create generic requirements here.
Yes. Probably with something like: > Note that a response to a QUERY request, is not identified by the target URI; see [ref to core].
Because QUERY will be considered by many as a drop-in replacement for GET, and may not realise this implication.
Just a random comment - I would buy both of you some drinks if you could figure out a way to express the [Set-]Cookie header data model in terms of...
If we don't add this, it might be good to note that a cacheble cookie's expiry happens relative to when the browser sees the cookie, so people aren't surprised.* *...