Skip to content

Commit 41baf41

Browse files
authored
Clarify query parameters for top-level self link
In the past we have seen several questions regarding the top-level `self` link and if it should contain query parameters supplied by the client, which affected the response document. Adding an explicit note about it should help to prevent such confusion in the future.
1 parent 0801766 commit 41baf41

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

_format/1.1/index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -319,6 +319,12 @@ The top-level [links object][links] **MAY** contain the following members:
319319
Schema) for the current document.
320320
* [pagination] links for the primary data.
321321

322+
> Note: The `self` link should contain the query parameters provided by the client
323+
> to generate the current response document. This includes but is not limited to
324+
> query parameters used for [inclusion of related resources][fetching resources],
325+
> [sparse fieldsets][fetching sparse fieldsets], [sorting][fetching sorting],
326+
> [pagination][fetching pagination] and [filtering][fetching filtering].
327+
322328
The document's "primary data" is a representation of the resource or collection
323329
of resources targeted by a request.
324330

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy